Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.dependencytrack/dependency-track
  4. ›
  5. CVE-2022-39351

CVE-2022-39351: Cleartext Storage of Sensitive Information

October 25, 2022 (updated October 28, 2022)

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

  • docs.dependencytrack.org/changelog/
  • github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml
  • github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4
  • nvd.nist.gov/vuln/detail/CVE-2022-39351

Code Behaviors & Features

Detect and mitigate CVE-2022-39351 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 4.6.0

Fixed versions

  • 4.6.0

Solution

Upgrade to version 4.6.0 or above.

Impact 4.4 MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Learn more about CVSS

Weakness

  • CWE-312: Cleartext Storage of Sensitive Information

Source file

maven/org.dependencytrack/dependency-track/CVE-2022-39351.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:16:01 +0000.