CVE-2022-39351
Dependecy-Track API Key Exposure
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.
INFO
Published Date :
Oct. 25, 2022, 5:15 p.m.
Last Modified :
Oct. 28, 2022, 7:24 p.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
0.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-39351.
| URL | Resource |
|---|---|
| https://docs.dependencytrack.org/changelog/ | Product Release Notes |
| https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml | Third Party Advisory |
| https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4 | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-39351 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-39351 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Oct. 28, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://docs.dependencytrack.org/changelog/ No Types Assigned https://docs.dependencytrack.org/changelog/ Product, Release Notes Changed Reference Type https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml No Types Assigned https://github.com/DependencyTrack/dependency-track/blob/4.5.0/src/main/docker/logback.xml Third Party Advisory Changed Reference Type https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4 No Types Assigned https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-gh7v-4hxp-gqp4 Third Party Advisory Added CWE NIST CWE-312 Added CPE Configuration OR *cpe:2.3:a:owasp:dependency-track:*:*:*:*:*:*:*:* versions up to (excluding) 4.6.0
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-39351 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-39351
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.05 }} 0.00%
score
0.16498
percentile