CVE-2022-39351 json
Dependency-Track vulnerable to logging of API keys in clear text when handling API requests using keys with insufficient permissions
published 2022-10-25 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-41821
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- owasp dependency-track 4.6.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected products
- DependencyTrack dependency-track
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
docs.dependencytrack.org
/changelog/
product, release-notes
-
github.com
/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4
third-party-advisory
-
github.com
/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml
third-party-advisory
Sources
- CVE List CVE-2022-39351
- NVD CVE-2022-39351
Fencer Vulns 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.