Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2024-28752 is a critical-severity SSRF (CWE-918) vulnerability in Apache Cxf. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 17% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-28752 is a server-side request forgery vulnerability that affects the Aegis DataBinding component in Apache CXF releases prior to 4.0.4, 3.6.3, and 3.5.8. The flaw is present only when this binding is in use and the exposed web service accepts at least one parameter of any type; services that rely on the default data binding or other bindings are unaffected. The issue is tracked as CWE-918 and carries a CVSS 3.1 score of 9.3.
An unauthenticated remote attacker can supply crafted input to a vulnerable service endpoint and cause the CXF instance to issue arbitrary outbound requests, achieving SSRF-style access to internal resources or external systems. The attack requires user interaction and results in high impact to confidentiality and integrity while leaving availability untouched.
Apache CXF security advisories direct users to upgrade to version 4.0.4, 3.6.3, or 3.5.8 or later. Corresponding vendor notices, including NetApp’s, reiterate the same remediation steps and list affected products that embed the vulnerable CXF library.
The EPSS score has reached a peak of 0.5714 with a current value of 0.5083, indicating sustained exploitation interest after public disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0991
Vulnerability Data
A SSRF vulnerability using the Aegis DataBinding in versions of Apache CXF before 4.0.4, 3.6.3 and 3.5.8 allows an attacker to perform SSRF style attacks on webservices that take at least one parameter of any type. Users of other data…
more
bindings (including the default databinding) are not impacted.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
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.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
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.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.