Cyber Resilience

CVE-2024-41146

Published
12 December 2024
Modified
15 April 2026
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0031 23th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2024-41146 is a medium-severity Use of Multiple Resources with Duplicate Identifier (CWE-694) vulnerability in Gallagher (inferred from references). Its CVSS base score is 4.6 (Medium).

Operationally, ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-4 (Identifier Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Use of Multiple Resources with Duplicate Identifier (CWE-694) in the Controller 6000 and Controller 7000 Platforms could allow an attacker with physical access to HBUS communication cabling to perform a Denial-of-Service attack against HBUS connected devices, require a device reboot…

more

to resolve. This issue affects: Controller 6000 and Controller 7000 firmware versions 9.10 prior to vCR9.10.241108a (distributed in 9.10.2149 (MR4)), 9.00 prior to vCR9.00.241108a (distributed in 9.00.2374 (MR5)), 8.90 prior to vCR8.90.241107a (distributed in 8.90.2356 (MR6)), all versions of 8.80 and prior.

CWE(s)
CWE-694

Related Threats

CVEs Like This One

CVE-2026-5794Shared CWE-694
CVE-2026-57024Shared CWE-694
CVE-2026-71327Shared CWE-694
CVE-2025-13609Shared CWE-694
CVE-2023-20100Shared CWE-694
CVE-2025-59048Shared CWE-694

Affected Assets

Gallagher
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V8.4.1
  • V3.5.4
  • V6.8.1
  • V9.2.4

Mitigating Controls (NIST 800-53 r5) AI

IA-4 Identifier Management good match

Identifier management directly requires authorization and uniqueness controls that stop duplicate resource identifiers from being assigned or used.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.AM-02 mostly match
prevents

Maintaining software/service inventories requires and enforces unique identifiers to avoid collisions.

PR.AA-01 mostly match
prevents

Managing identities and credentials for users/services/hardware directly requires unique identifiers.

ID.AM-08 partial match
prevents

Lifecycle management of assets includes identifier uniqueness as a supporting practice.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect duplicate identifiers before deployment.

A.5.16 Identity management partial match
prevents

Identity management processes that enforce unique identifiers directly prevent duplicate resource IDs.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can catch duplicate-ID issues during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards can mandate unique identifier generation and validation.

A.8.9 Configuration management partial match
degrades

Configuration management ensures unique identifiers are assigned and maintained across resources.

References