Dependency-Track up to 4.5.x API Request cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Dependency-Track up to 4.5.x. Affected is an unknown function of the component API Request Handler. Executing a manipulation can lead to cleartext storage. This vulnerability is handled as CVE-2022-39351. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in Dependency-Track up to 4.5.x. This vulnerability affects an unknown code block of the component API Request Handler. The manipulation with an unknown input leads to a cleartext storage vulnerability. The CWE definition for the vulnerability is CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The weakness was released 10/26/2022 as GHSA-gh7v-4hxp-gqp4. The advisory is available at github.com. This vulnerability was named CVE-2022-39351 since 09/02/2022. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1555 by the MITRE ATT&CK project.
Upgrading to version 4.6.0 eliminates this vulnerability. The upgrade is hosted for download at docs.dependencytrack.org.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-41821). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.4
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Dependency-Track 4.6.0
Timeline
09/02/2022 🔍10/26/2022 🔍
10/26/2022 🔍
06/30/2026 🔍
Sources
Advisory: GHSA-gh7v-4hxp-gqp4Status: Confirmed
CVE: CVE-2022-39351 (🔍)
GCVE (CVE): GCVE-0-2022-39351
GCVE (VulDB): GCVE-100-212266
EUVD: 🔍
Entry
Created: 10/26/2022 09:14Updated: 06/30/2026 15:38
Changes: 10/26/2022 09:14 (51), 06/30/2026 15:38 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.