CVE-2022-39351 Information disclosure in dependency-track
Attackers with audit log access can steal API keys logged in clear text, potentially leading to unauthorized access to the Dependency-Track platform.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-39351?
CVE-2022-39351 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 25 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
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.
Weakness: CWE-312
Which versions are affected by CVE-2022-39351?
It affects 1 product.
Products include Owasp Dependency-Track.
How do I fix CVE-2022-39351?
No fix has been published for CVE-2022-39351 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-39351 being exploited?
There is no known exploitation of CVE-2022-39351 in the wild and no public exploit code.
Other vulnerabilities in DependencyTrack dependency-track
Sources
Also known as GHSA-gh7v-4hxp-gqp4.