nvdApiKey is logged in debug mode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.

Published by the source

15 Dec 2023, 23:43 UTC

Last modified by the source

22 Jan 2024, 21:14 UTC

Source last checked

26 Oct 2026, 16:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qqhq-8r2c-c3f5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qqhq-8r2c-c3f5

Advisory: nvdApiKey is logged in debug mode
IDs: GHSA-qqhq-8r2c-c3f5
Record: https://patchnext.com/advisories/ghsa-qqhq-8r2c-c3f5 (revision 1, source checked 26 Oct 2026, 16:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.owasp:dependency-check-cli 9.0.6; org.owasp:dependency-check-maven 9.0.6; org.owasp:dependency-check-ant 9.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.owasp:dependency-check-cli: affected >= 9.0.0, <= 9.0.5; fixed in 9.0.6
- Maven org.owasp:dependency-check-maven: affected >= 9.0.0, < 9.0.6; fixed in 9.0.6
- Maven org.owasp:dependency-check-ant: affected >= 9.0.0, <= 9.0.5; fixed in 9.0.6

## Suggested inspection (read-only)
- Maven org.owasp:dependency-check-cli: check the installed version with your package manager.
- Maven org.owasp:dependency-check-maven: check the installed version with your package manager.
- Maven org.owasp:dependency-check-ant: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.owasp:dependency-check-cli, org.owasp:dependency-check-maven, org.owasp:dependency-check-ant.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qqhq-8r2c-c3f5 (GitHub-reviewed advisory GHSA-qqhq-8r2c-c3f5 lists affected ranges: Maven org.owasp:dependency-check-ant >=9.0.0 =9.0.0 =9.0.0 <9.0.6)

Commands are suggestions: review each one before running it.