CVE-2022-39351

low-risk
Published 2022-10-25

Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions causes the API key to be written to Dependency-Track's audit log in clear text. Actors with access to the audit log can exploit this flaw to gain access to valid API keys. The issue has been fixed in Dependency-Track 4.6.0. Instead of logging the entire API key, only the last 4 characters of the key will be logged. It is strongly recommended to check historic logs for occurrences of this behavior, and re-generating API keys in case of leakage.

Do I need to act?

-
0.03% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
4
CVSS 4.4/10 Medium
LOCAL / LOW complexity

Affected Products (1)

Dependency-Track

Affected Vendors

Owasp

References (6)

Product https://docs.dependencytrack.org/changelog/
Third Party Advisory https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/l...
Third Party Advisory https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7...
Product https://docs.dependencytrack.org/changelog/
Third Party Advisory https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/l...
Third Party Advisory https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7...
20
/ 100
low-risk
Severity 15/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal