CVEvulnerability
CVE-2022-39351
4.4 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2022-10-25
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 4.4 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CVSS 3.1 ([email protected])
- 4.4 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- CWE-312
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 configurations
• owasp dependency-track (< 4.6.0)
Related
Weakness · CWE (1)
- CWE-312 Cleartext Storage of Sensitive Information weakness
References
- 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
- 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