Cyber Resilience

CVE-2024-25015

Ibm Mq 9.2.0.0 – 9.2.0.25

Published
01 May 2024
Modified
21 August 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0092 57th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2024-25015 is a high-severity Network Amplification (CWE-406) vulnerability in Ibm Mq. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Denial of Service (T1498); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SI-4 (System Monitoring) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IBM MQ 9.2 LTS, 9.3 LTS, and 9.3 CD Internet Pass-Thru could allow a remote user to cause a denial of service by sending HTTP requests that would consume all available resources. IBM X-Force ID: 281278.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1498 Network Denial of Service Impact
Adversaries may perform Network Denial of Service (DoS) attacks to degrade or block the availability of targeted resources to users.
T1498.002 Reflection Amplification Impact
Adversaries may attempt to cause a denial of service (DoS) by reflecting a high-volume of network traffic to a target.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-52898Same product: Ibm Linux On Ibm Z
CVE-2024-52896Same product: Ibm Linux On Ibm Z
CVE-2024-52897Same product: Ibm Linux On Ibm Z
CVE-2026-6052Same product: Ibm Aix
CVE-2026-6051Same product: Ibm Aix
CVE-2025-33126Same product: Ibm Aix
CVE-2025-33133Same product: Ibm Aix
CVE-2024-41783Same product: Ibm Aix
CVE-2023-50308Same product: Ibm Aix
CVE-2023-35020Same product: Ibm Aix

Affected Assets

ibm
mq
9.2.0.0 — 9.2.0.25 · 9.3.0 — 9.3.5 · 9.3.0.0 — 9.3.0.17

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Denial-of-service protection directly requires mechanisms to limit excessive outbound traffic volume that amplification attacks exploit.

System monitoring detects anomalous traffic volumes indicative of amplification after the weakness is present.

Boundary protection at managed interfaces enforces controls on communications volume and flow that can stop amplification.

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.

DE.CM-01 mostly match
prevents

Network monitoring directly detects anomalous traffic volumes that indicate amplification abuse.

PR.IR-04 partial match
prevents

Bandwidth monitoring supports capacity planning that can surface volume problems but does not enforce message-volume controls.

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.

finds

Monitoring activities can detect anomalous traffic volumes, yet detection alone does not enforce control.

A.8.15 Logging partial match
finds

Logging provides visibility into high-volume traffic but does not itself limit or control it.

mitigates

Network security controls include traffic filtering and rate-limiting that prevent amplification attacks.

mitigates

Security of network services can impose volume controls on specific services, but does not address the weakness broadly.

degrades

Capacity management directly limits excessive outbound traffic that an actor could otherwise trigger.

References