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.
References
Link | Resource |
---|---|
https://docs.dependencytrack.org/changelog/ | Product Release Notes |
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 | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: GitHub_M
Published: 2022-10-25T00:00:00
Updated: 2022-10-25T00:00:00
Reserved: 2022-09-02T00:00:00
Link: CVE-2022-39351
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-10-25T17:15:56.613
Modified: 2022-10-28T19:24:35.790
Link: CVE-2022-39351
JSON object: View
Redhat Information
No data.
CWE