Vulnerabilities · 2022 · Owasp
CVE-2022-39351
Owasp Dependency-track vulnerability
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
Dependency-track. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Owasp Dependency-track runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml · Third Party Advisory
- github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4 · Third Party Advisory
- docs.dependencytrack.org/changelog/
- nvd.nist.gov/vuln/detail/CVE-2022-39351
- cve.org/CVERecord?id=CVE-2022-39351
More vulnerabilities in Owasp products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.