# CVE-2024-28752: Apache CXF SSRF Vulnerability using the Aegis databinding > Attackers can perform Server-Side Request Forgery attacks on web services using the Aegis databinding in Apache CXF. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 Mar 2024 - **Updated:** 13 Feb 2025 - **Also known as:** GHSA-qmgx-j96g-4428 ## What is CVE-2024-28752? CVE-2024-28752 is a critical server-side request forgery vulnerability in Apache Cxf, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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 bindings (including the default databinding) are not impacted. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2024-28752? 6 open source packages ship an affected version, including org.apache.cxf:cxf-rt-databinding-aegis. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | All versions | 3.5.8 | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | All versions | 3.5.8 | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | From 3.6.0 | 3.6.3 | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | From 3.6.0 | 3.6.3 | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | From 4.0.0 | 4.0.4 | | `org.apache.cxf:cxf-rt-databinding-aegis` | Maven | From 4.0.0 | 4.0.4 | Products: Apache Cxf, Netapp Oncommand Workflow Automation, Netapp Ontap Tools. ## How do I fix CVE-2024-28752? Upgrade org.apache.cxf:cxf-rt-databinding-aegis to a fixed version for your release line: 3.5.8, 3.6.3 or 4.0.4. ## Is CVE-2024-28752 being exploited? There is no known exploitation of CVE-2024-28752 in the wild and no public exploit code. Public exploit code: - Apache CXF SSRF CVE-2024-28752 (github_poc): https://github.com/ReaJason/CVE-2024-28752 - Vulhub apache-cxf/CVE-2024-28752: Apache CXF Aegis DataBinding SSRF (CVE-2024-28752), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-apache-cxf-cve-2024-28752 ## Other vulnerabilities in Apache Cxf - [CVE-2012-2379](https://insights.sbomify.com/CVE-2012-2379/): XML Signature/Encryption Not Validated in Apache CXF (critical 10.0) - [CVE-2026-66909](https://insights.sbomify.com/CVE-2026-66909/): Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage (critical 9.8) - [CVE-2026-68079](https://insights.sbomify.com/CVE-2026-68079/): Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay (critical 9.8) - [CVE-2026-50628](https://insights.sbomify.com/CVE-2026-50628/): Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control (critical 9.8) - [CVE-2025-48913](https://insights.sbomify.com/CVE-2025-48913/): Apache CXF: Untrusted JMS configuration can lead to RCE (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-28752 and fix it if it is affected. What it is: CVE-2024-28752 is a critical server-side request forgery vulnerability in Apache Cxf, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-28752 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected all versions; fixed in 3.5.8 - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected all versions; fixed in 3.5.8 - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected from 3.6.0; fixed in 3.6.3 - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected from 3.6.0; fixed in 3.6.3 - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected from 4.0.0; fixed in 4.0.4 - org.apache.cxf:cxf-rt-databinding-aegis (Maven): affected from 4.0.0; fixed in 4.0.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-28752/ (Markdown: https://insights.sbomify.com/CVE-2024-28752/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28752 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28752 - OSV: https://osv.dev/vulnerability/CVE-2024-28752 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28752/ Summaries are generated and may contain mistakes; the official description above is the record.