Vulnerability in Dependencytrack Dependency-Track
CVE-2022-39351
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.
EPSS: 0.002 (9.8th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 4.4 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N.
Affected products
- Dependencytrack Dependency-track — versions < 4.6.0
- Owasp Dependency-track
Weakness classification (CWE)
References
- security-advisories@github.com (Product, Release Notes)
- security-advisories@github.com (Third Party Advisory)
- security-advisories@github.com (Third Party Advisory)
Frequently asked questions
- What is CVE-2022-39351?
- CVE-2022-39351 is a medium-severity vulnerability in Dependencytrack Dependency-Track, classified under Cleartext Storage of Sensitive Information. CVSS score: 4.4/10. Published 2022-10-25.
- How severe is CVE-2022-39351?
- Medium severity. CVSS v3 base score is 4.4 out of 10.