dbcve.org
CxfApplication · Apache

CVE-2024-28752

CRITICAL · 9.3 CVSS v3.1 Published 2024-03-15
Fix available
A fix is available. Upgrade to 3.5.8 / 3.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache CXF contains an SSRF vulnerability in the Aegis DataBinding component. Versions before 4.0.4, 3.6.3, and 3.5.8 allow attackers to manipulate webservices using Aegis databinding to make the server perform arbitrary HTTP requests to attacker-controlled destinations. Services using other data bindings (including default) are unaffected.

MitigationUpgrade Apache CXF to version 4.0.4, 3.6.3, or 3.5.8 or later. Alternatively, migrate away from the Aegis databinding to an unaffected binding such as the default JAXB data binding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CxfApplication
Affected:< 3.5.8>= 3.6.0, < 3.6.3>= 4.0.0, < 4.0.4
Oncommand Workflow AutomationApplication
Affected:all versions
Ontap ToolsApplication
Affected:= 10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache CXF version in use
    Check the CXF library version by examining pom.xml dependencies, MANIFEST.MF files in CXF jars, or by listing the cxf-core JAR file name in your deployment. Command example: find . -name 'cxf-core*.jar' -o -name 'cxf*.jar' | xargs -I {} basename {}
    Affected if The CXF version is < 3.5.8, >= 3.6.0 and < 3.6.3, or >= 4.0.0 and < 4.0.4
  2. Verify Aegis databinding is configured
    Search for Aegis databinding configuration in your CXF service configuration XML files. Look for elements such as <aegis:databinding/> or imports of Aegis-related namespaces (commonly http://apache.org/cxf/aegis). Search command: grep -r 'aegis' --include='*.xml' .
    Affected if Aegis databinding is explicitly configured or referenced in your service configuration files
  3. Check for Aegis dependencies in build files
    Examine pom.xml or build.gradle for Aegis-related dependencies such as cxf-rt-databinding-aegis. Search command: grep -i 'aegis' pom.xml
    Affected if The cxf-rt-databinding-aegis dependency is present in your build configuration
  4. Inspect Java source code for Aegis usage
    Search Java source files for Aegis imports or annotations. Look for patterns like 'import org.apache.cxf.aegis.*' or references to AegisType or AegisWriter. Command: find . -name '*.java' -exec grep -l 'cxf.aegis' {} \;
    Affected if Your source code contains explicit imports or instantiations of Aegis databinding classes

You are affected only if your deployment uses a vulnerable Apache CXF version AND explicitly uses the Aegis databinding component; using default JAXB or other bindings means you are not affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.5.8 / 3.6.3 / 4.0.4 or later
Fixed in 3.5.83.6.34.0.4
Interim mitigation

Upgrade Apache CXF to version 4.0.4, 3.6.3, or 3.5.8 or later. Alternatively, migrate away from the Aegis databinding to an unaffected binding such as the default JAXB data binding.

Recommended fix Moderate confidence

CXF 3.5.8, 3.6.3, or 4.0.4 (depending on your current major.minor version)

  1. 1. Identify if your CXF application uses the Aegis DataBinding by checking your Spring or code configuration for 'AegisDataBinding' or 'aegis' databinding settings
  2. 2. If you are NOT using Aegis DataBinding, this vulnerability does not affect you - you can continue using your current version
  3. 3. If you ARE using Aegis DataBinding, determine your current CXF version from your Maven pom.xml or dependencies
  4. 4. If using CXF 3.x: upgrade to 3.5.8 or 3.6.3 (depending on your current minor version)
  5. 5. If using CXF 4.x: upgrade to 4.0.4
  6. 6. Update your Maven pom.xml or build configuration to use the new version
  7. 7. Rebuild and redeploy your application
  8. 8. Test that your webservices using Aegis DataBinding still function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cxf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28752 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data