Skip to content
Fencer Intel
medium 5.3

CVE-2024-23686 json

DependencyCheck Debug Mode Logging of NVD API Key

published 2y ago modified 3d ago also EUVD-2024-0347 , GHSA-frxm-v7q3-v2wv , GHSA-qqhq-8r2c-c3f5

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

DependencyCheck for Maven 9.0.0 to 9.0.6, for CLI version 9.0.0 to 9.0.5, and for Ant versions 9.0.0 to 9.0.5, when used in debug mode, allows an attacker to recover the NVD API Key from a log file.

Patch / fix

  • maven org.owasp:dependency-check-ant 9.0.6
  • maven org.owasp:dependency-check-cli 9.0.6
  • maven org.owasp:dependency-check-maven 9.0.6
  • owasp dependency-check 9.0.6

Is CVE-2024-23686 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.owasp:dependency-check-ant
>=9.0.0, <9.0.6
9.0.6
maven org.owasp:dependency-check-cli
>=9.0.0, <9.0.6
9.0.6
maven org.owasp:dependency-check-maven
>=9.0.0, <9.0.6
9.0.6

Affected products

  • org.owasp org.owasp:dependency-check-maven
  • org.owasp org.owasp:dependency-check-cli
  • org.owasp org.owasp:dependency-check-ant

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.