Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2022-39351

4.4 · MEDIUM
Published Oct 25, 2022 owasp CWE-312 EPSS 0.21% (11th pctl)

Overview

CVE-2022-39351 is a medium-severity vulnerability affecting owasp dependency-track. It was published on October 25, 2022 and has a CVSS 3.1 base score of 4.4 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 4.4, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories and patches from owasp. Update dependency-track to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
owasp dependency-track >= 0, < 4.6.0 Affected

Frequently Asked Questions

What is CVE-2022-39351?

CVE-2022-39351 is a medium-severity vulnerability affecting owasp dependency-track. It was published on October 25, 2022 and has a CVSS 3.1 base score of 4.4 (MEDIUM).

How severe is CVE-2022-39351?

This vulnerability has a CVSS 3.1 base score of 4.4, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-39351?

Check the references section for vendor advisories and patches from owasp. Update dependency-track to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-39351?

CyberStrike's AI-powered security agents can automatically detect CVE-2022-39351 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.