dbcve.org
CxfApplication · Apache

CVE-2024-29736

CRITICAL · 9.1 CVSS v3.1 Published 2024-07-19
Fix available
A fix is available. Upgrade to 3.5.9 / 3.6.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 in WADL service description in versions of Apache CXF before 4.0.5, 3.6.4 and 3.5.9 allows an attacker to perform SSRF style attacks on REST webservices. The attack only applies if a custom stylesheet parameter is configured.

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 before versions 4.0.5, 3.6.4, and 3.5.9 contains a Server-Side Request Forgery (SSRF) vulnerability in the WADL (Web Application Description Language) service description feature. When a custom stylesheet parameter is configured, an attacker can manipulate the WADL service to make the server perform unintended requests to internal or external resources.

MitigationUpgrade Apache CXF to version 4.0.5, 3.6.4, or 3.5.9 or later. If upgrading is not immediately possible, avoid configuring custom stylesheet parameters for WADL services.

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.9>= 3.6.0, < 3.6.4>= 4.0.0, < 4.0.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
    Locate the CXF JAR files or dependencies in your application (check pom.xml, lib directory, or build artifacts) and note the exact version number present in your environment
    Affected if The installed version falls within < 3.5.9, >= 3.6.0 and < 3.6.4, or >= 4.0.0 and < 4.0.5
  2. Determine if WADL generation is enabled
    Search your application configuration files (such as web.xml, Spring or Blueprint XML configs, or JAX-RS annotations) for WADL-related configuration such as WadlFeature, WadlGenerator, or wadl=true parameters
    Affected if WADL generation is enabled in your CXF configuration
  3. Check for custom stylesheet configuration in WADL
    Search CXF configuration files and application code for any custom stylesheet parameters related to WADL, such as stylesheetLocation, customStylesheet, or similar parameters passed to WADL features
    Affected if A custom stylesheet parameter is configured for the WADL service description feature

You are affected if your Apache CXF version is below 4.0.5 (or between 3.6.0-3.6.3, or below 3.5.9) AND WADL with a custom stylesheet parameter is enabled in your environment

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.9 / 3.6.4 / 4.0.5 or later
Fixed in 3.5.93.6.44.0.5
Interim mitigation

Upgrade Apache CXF to version 4.0.5, 3.6.4, or 3.5.9 or later. If upgrading is not immediately possible, avoid configuring custom stylesheet parameters for WADL services.

Recommended fix High confidence

Apache CXF 4.0.5 (or 3.6.4 or 3.5.9 depending on current branch)

  1. 1. Identify the current Apache CXF version in use by checking project dependencies (pom.xml, build.gradle, or similar)
  2. 2. Determine which version branch is currently in use (3.5.x, 3.6.x, or 4.x)
  3. 3. If using 4.0.0-4.0.4: upgrade to 4.0.5 or later
  4. 4. If using 3.6.0-3.6.3: upgrade to 3.6.4 or later
  5. 5. If using any version < 3.5.9: upgrade to 3.5.9 or later
  6. 6. Update the dependency version in your build configuration file
  7. 7. Rebuild and test the application to ensure compatibility
  8. 8. Verify the WADL service description functionality works correctly after upgrade
Caveat Minor point releases typically contain bug fixes without breaking changes; verify release notes for any relevant changes

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

Fix this in Cxf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29736 — 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-29736 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