CxfApplication · Apache
CVE-2024-41172
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 · uneditedIn versions of Apache CXF before 3.6.4 and 4.0.5 (3.5.x and lower versions are not impacted), a CXF HTTP client conduit may prevent HTTPClient instances from being garbage collected and it is possible that memory consumption will continue to increase, eventually causing the application to run out of memory
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 confidenceApache CXF HTTP client conduit prevents proper garbage collection of HTTPClient instances in versions 3.6.0-3.6.3 and 4.0.0-4.0.4, causing gradual memory accumulation that leads to out-of-memory conditions.
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
>= 3.6.0, < 3.6.4>= 4.0.0, < 4.0.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache CXF version in useLocate the CXF JAR files or dependency declaration (e.g., pom.xml, lib directory) and read the version number from the filename, MANIFEST.MF, or dependency managementAffected if The version falls within >= 3.6.0 to < 3.6.4 or >= 4.0.0 to < 4.0.5
-
Confirm HTTP client conduit is in useDetermine whether your application configures or programmatically creates an HTTP client conduit through CXF configuration files (XML beans) or client proxyfactory codeAffected if HTTP client conduit is explicitly configured or implicitly instantiated by your CXF client code
-
Monitor for memory accumulationObserve JVM heap usage over time under sustained CXF HTTP client traffic. Use JConsole, VisualVM, or heap dumps to track if heap grows consistently without full GC recoveryAffected if Heap usage shows steady increase across multiple GC cycles during normal client operations and eventually approaches exhaustion
You are affected if your CXF version is 3.6.0-3.6.3 or 4.0.0-4.0.4 AND you make use of the HTTP client conduit, as only that component contains the leak.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.6.44.0.5
Upgrade Apache CXF to version 3.6.4, 4.0.5, or later to resolve the memory leak in the HTTP client conduit.
Apache CXF 3.6.4 or later, or Apache CXF 4.0.5 or later
- Identify the current Apache CXF version in use by checking project dependencies (Maven pom.xml, Gradle build.gradle, or bundled JAR version)
- If using CXF 3.6.x, upgrade to version 3.6.4 or later
- If using CXF 4.0.x, upgrade to version 4.0.5 or later
- For Maven projects, update the CXF dependency version in pom.xml (e.g., change <version>3.6.0</version> to <version>3.6.4</version>)
- Rebuild and redeploy the application
- Monitor application memory usage after deployment to verify the memory leak is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cxf
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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