Vulnerability · Published Oct 25, 2022 · Assigned by GitHub_M
CVE-2022-39351Dependency-Track vulnerable to logging of API keys in clear text when handling API requests using keys with insufficient permissions
Medium 4.4
In plain English
A medium-severity security flaw in dependency-track from DependencyTrack. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities).
Official 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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| DependencyTrack | dependency-track | < 4.6.0 |
Weakness: CWE-312 · Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N