Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
MEDIUM severity

GHSA-jqh2-ch7p-xwxh

MEDIUMFix: quarkiverse/quarkus-cxf@8ed72ca

GHSA-jqh2-ch7p-xwxh is a medium-severity (CVSS 5.3) CWE-532 vulnerability in io.quarkiverse.cxf:quarkus-cxf. O3 Security confirms whether GHSA-jqh2-ch7p-xwxh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus CXF logs passwords and other secrets

Also known asCVE-2024-9621
Published
Oct 8, 2024
Updated
Dec 6, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 6, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
io.quarkiverse.cxf:quarkus-cxf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A 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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.quarkiverse.cxf:quarkus-cxfall versions3.15.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkiverse.cxf:quarkus-cxf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update io.quarkiverse.cxf:quarkus-cxf to 3.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqh2-ch7p-xwxh is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jqh2-ch7p-xwxh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jqh2-ch7p-xwxh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A 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.
O3 Security · Impact-Aware SCA

Is GHSA-jqh2-ch7p-xwxh in your dependencies?

O3 detects GHSA-jqh2-ch7p-xwxh across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.