CVE-2024-28787
Ibm Application Gateway 20.01 – 24.03
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:HSummary
CVE-2024-28787 is a high-severity Trusting HTTP Permission Methods on the Server Side (CWE-650) vulnerability in Ibm Application Gateway. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-25873
Vulnerability Data
IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote attacker to obtain highly sensitive private information or cause a denial of service using a specially crafted HTTP request. IBM X-Force ID:…
more
286584.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.1V3.5.3V4.1.4
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces authorizations for resource access without permitting unsafe assumptions about request methods to bypass checks.
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.
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.
Security testing can detect and prevent vulnerabilities where GET requests cause unintended state changes.
Application security requirements can mandate proper HTTP method usage and state-changing operation restrictions.
Secure system architecture principles include proper HTTP method handling and RESTful design to prevent state changes via GET.
Secure coding practices directly address improper HTTP method usage and ensure state-changing operations use POST/PUT/DELETE.