CVE-2024-54173
Ibm Mq Appliance ≤ 9.4.2
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-54173 is a medium-severity Improper Management of Sensitive Trace Data (CWE-1323) vulnerability in Ibm Mq Appliance. Its CVSS base score is 4.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 3th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53952
Vulnerability Data
IBM MQ 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD reveals potentially sensitive information in trace files that could be read by a local user when webconsole trace is enabled.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so sensitive trace data cannot be stored or accessed in unprotected locations.
Enforces information flow policies that block trace data from reaching untrusted agents or destinations.
Requires protection of information at rest, directly stopping storage of trace data in unprotected locations.
Requires confidentiality and integrity protection for all transmitted trace data, directly stopping exposure in transit.
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.
Protecting data-at-rest directly prevents storage of trace data in unprotected locations.
Protecting data-in-transit directly prevents transport of trace data to untrusted agents.
Protecting data-in-use can limit exposure during trace collection or processing.
Requiring protected log generation and handling indirectly covers sensitive trace data as a form of logging.
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.
DLP mechanisms can detect and block exfiltration of trace data.
Technical access restrictions directly prevent unauthorized access to trace storage.
Classification identifies trace data as sensitive, guiding its protection.
Rules for secure transfer reduce exposure when trace data leaves the SoC.
Access-control policies limit who can read or move trace buffers.
Logging controls define where and how trace data may be stored.