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.
Published 2022-10-25 17:15:57
Updated 2022-10-28 19:24:36
Source GitHub, Inc.
View at NVD,   CVE.org

Products affected by CVE-2022-39351

Exploit prediction scoring system (EPSS) score for CVE-2022-39351

0.05%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 16 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2022-39351

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
4.4
MEDIUM CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
0.8
3.6
NIST
4.4
MEDIUM CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
0.8
3.6
GitHub, Inc.

CWE ids for CVE-2022-39351

  • The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
    Assigned by:
    • nvd@nist.gov (Primary)
    • security-advisories@github.com (Secondary)

References for CVE-2022-39351

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!