Medium severity · published Oct 25, 2022
CVE-2022-39351
Dependency-Track vulnerable to logging of API keys in clear text when handling API requests using keys with insufficient permissions
4.4
CVSS
0.2%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 12% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DE
dependency-track · DependencyTrack
< 4.6.0 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-39351
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-39351
Product
https://docs.dependencytrack.org/changelog/
Third Party Advisory
https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml
Third Party Advisory
https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4
