Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
DependencyTrack dependency-track
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Dependency-Track是一套用于识别第三方组件风险的智能供应链组件分析平台。 Dependency-Track 4.6.0之前版本存在安全漏洞，该漏洞源于使用权限不足的有效API密钥执行API请求会导致API密钥以明文形式写入Dependency-Track的审核日志，有权访问审计日志的参与者可以利用此漏洞来访问有效的API密钥。

CVSS 4.4 · Medium EPSS 0.21% · P10

Possible ATT&CK Techniques 1 AI

T1552 · Unsecured Credentials
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-39351

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Dependency-Track vulnerable to logging of API keys in clear text when handling API requests using keys with insufficient permissions
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
敏感数据的明文存储
Source: CVE Program / CVE List V5
Vulnerability Title
Dependency-Track 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Dependency-Track是一套用于识别第三方组件风险的智能供应链组件分析平台。 Dependency-Track 4.6.0之前版本存在安全漏洞，该漏洞源于使用权限不足的有效API密钥执行API请求会导致API密钥以明文形式写入Dependency-Track的审核日志，有权访问审计日志的参与者可以利用此漏洞来访问有效的API密钥。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
DependencyTrack dependency-track < 4.6.0 -

II. Public POCs for CVE-2022-39351

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-39351

请登录查看更多情报信息。

Vendor Advisories for CVE-2022-39351 (1)

Other References for CVE-2022-39351 (2)

IV. Related Vulnerabilities

Same product: dependency-track
Same vendor: DependencyTrack
Same weakness: CWE-312

V. Comments for CVE-2022-39351

No comments yet

Leave a comment