Skip to content

nvdApiKey is logged in debug mode

Low severity GitHub Reviewed Published Dec 15, 2023 in jeremylong/DependencyCheck • Updated Jan 22, 2024

Package

maven org.owasp:dependency-check-ant (Maven)

Affected versions

>= 9.0.0, <= 9.0.5

Patched versions

9.0.6
maven org.owasp:dependency-check-cli (Maven)
>= 9.0.0, <= 9.0.5
9.0.6
maven org.owasp:dependency-check-maven (Maven)
>= 9.0.0, < 9.0.6
9.0.6

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.

References

@jeremylong jeremylong published to jeremylong/DependencyCheck Dec 15, 2023
Published to the GitHub Advisory Database Dec 15, 2023
Reviewed Dec 15, 2023
Last updated Jan 22, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-qqhq-8r2c-c3f5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.