CVE-2024-9621
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 · uneditedA vulnerability was found in Quarkus CXF. Passwords and other secrets may appear in the application log in spite of the user configuring them to be hidden. This issue requires some special configuration to be vulnerable, such as SOAP logging enabled, application set client, and endpoint logging properties, and the attacker must have access to the application log.
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 confidenceQuarkus CXF has a logging configuration vulnerability where passwords and secrets can leak into application logs despite users configuring them to be hidden. The leak occurs when SOAP logging is enabled with specific client and endpoint logging properties, allowing an attacker with log access to obtain sensitive credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Quarkus CXF usageSearch your project dependencies (pom.xml, build.gradle, or runtime classpath) for 'quarkus-cxf' or 'cxf' dependencies. Check application configuration files (application.properties or application.yaml) for CXF-related settings.Affected if Quarkus CXF dependency is present in the project
-
Determine Quarkus CXF versionReview your dependency management to find the exact version of quarkus-cxf. In Maven, run 'mvn dependency:list' or inspect pom.xml. In Gradle, run 'gradle dependencies'.Affected if The installed version falls within an affected range (compare to any published vulnerable versions for this CVE)
-
Verify SOAP logging is enabledInspect your application.properties, application.yaml, or any CXF-specific configuration files for properties such as 'quarkus.cxf.client.*.logging' or 'quarkus.cxf.endpoint.*.logging' set to 'true'. Also check for 'org.apache.cxf' logger configurations in logging configuration files.Affected if SOAP logging is enabled via client or endpoint logging properties (any logging feature that captures SOAP messages)
-
Check for sensitive property exposureReview current application logs and any archived logs for patterns matching passwords, secrets, API keys, or tokens. Search for strings like 'password=', 'secret=', 'token=', or credential values that may have been configured as properties.Affected if Sensitive credentials configured in CXF client or endpoint properties appear in application logs despite being marked as sensitive
A user is affected if they use Quarkus CXF with SOAP logging enabled and sensitive credentials are being logged despite configuration attempts to hide them.
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.
From vendor dataRestrict access to application logs, disable SOAP logging when not needed, and verify that sensitive properties are not being logged through endpoint configuration.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9621 — 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-9621 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