CVE-2022-39351
Summary
| CVE | CVE-2022-39351 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-10-25 17:15:00 UTC |
| Updated | 2022-10-28 19:24:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-312
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Owasp | Dependency-track | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Logging of API keys in clear text when handling API requests using keys with insufficient permissions · Advisory · DependencyTrack/dependency-track · GitHub | CONFIRM | github.com | |
| dependency-track/logback.xml at 4.5.0 · DependencyTrack/dependency-track · GitHub | MISC | github.com | |
| Change Log | Dependency-Track | MISC | docs.dependencytrack.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.