Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-qqhq-8r2c-c3f5

LOW

nvdApiKey is logged in debug mode

Published
Dec 15, 2023
Updated
Feb 4, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
org.owasp:dependency-check-antorg.owasp:dependency-check-cliorg.owasp:dependency-check-maven

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

Summary

The value of nvdApiKey configuration parameter is logged in clear text in debug mode.

Details

The NVD API key is a kind of secret and should be treated like other secrets when logging in debug mode. Expecting the same behavior as for several password configurations: just print ******

Note that while the NVD API Key is an access token for the NVD API - they are not that sensitive. The only thing an NVD API Token grants is a higher rate limit when making calls to publicly available data. The data available from the NVD API is the same whether you have an API Key or not.

PoC

The nvdApiKey is configured to use an environment variable; when running mvn -X dependency-check:check the clear value is logged twice.

Impact

The NVD API key is a kind of secret and should not be exposed. If stolen, an attacker can use this key to obtain already public information.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.owasp:dependency-check-ant9.0.0&&< 9.0.69.0.6
Mavenorg.owasp:dependency-check-cli9.0.0&&< 9.0.69.0.6
Mavenorg.owasp:dependency-check-maven9.0.0&&< 9.0.69.0.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp:dependency-check-ant. 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 org.owasp:dependency-check-ant to 9.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqhq-8r2c-c3f5 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-qqhq-8r2c-c3f5 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-qqhq-8r2c-c3f5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The value of `nvdApiKey` configuration parameter is logged in clear text in debug mode. ### Details The NVD API key is a kind of secret and should be treated like other secrets when logging in debug mode. Expecting the same behavior as for several password configurations: just print `******` Note that while the NVD API Key is an access token for the NVD API - they are not that sensitive. The only thing an NVD API Token grants is a higher rate limit when making calls to publicly available data. The data available from the NVD API is the same whether you have an API Key or not. ##
O3 Security · Impact-Aware SCA

Is GHSA-qqhq-8r2c-c3f5 in your dependencies?

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