What is CVE-2022-39351?

CVE-2022-39351 is a vulnerability in Dependency-Track software that allows an API key with insufficient permissions to be logged in the audit log.

How does CVE-2022-39351 impact Dependency-Track?

CVE-2022-39351 impacts Dependency-Track by leaking API keys to the audit log when making an API request with insufficient permissions.

What is the severity of CVE-2022-39351?

The severity of CVE-2022-39351 is medium, with a severity value of 4.4.

How can I fix CVE-2022-39351?

To fix CVE-2022-39351, you should update Dependency-Track to version 4.6.0 or higher.

What is the Common Weakness Enumeration (CWE) for CVE-2022-39351?

The CWE for CVE-2022-39351 is CWE-312 (Cleartext Storage of Sensitive Information in a Log File).

Vulnerability/
CVE-2022-39351

medium

4.4

CWE

312

25/10/2022

23/4/2025

CVE-2022-39351: Dependency-Track vulnerable to logging of API keys in clear text when handling API requests using keys with insufficient permissions

First published: Tue Oct 25 2022(Updated: )

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.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
Dependency-Track	<4.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2022-39351?
CVE-2022-39351 is a vulnerability in Dependency-Track software that allows an API key with insufficient permissions to be logged in the audit log.
How does CVE-2022-39351 impact Dependency-Track?
CVE-2022-39351 impacts Dependency-Track by leaking API keys to the audit log when making an API request with insufficient permissions.
What is the severity of CVE-2022-39351?
The severity of CVE-2022-39351 is medium, with a severity value of 4.4.
How can I fix CVE-2022-39351?
To fix CVE-2022-39351, you should update Dependency-Track to version 4.6.0 or higher.
What is the Common Weakness Enumeration (CWE) for CVE-2022-39351?
The CWE for CVE-2022-39351 is CWE-312 (Cleartext Storage of Sensitive Information in a Log File).

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/title
agent/severity
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/owasp
canonical/dependency-track

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.