{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39351 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39351 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 25 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39351 and fix it if it is affected.\n\nWhat it is: CVE-2022-39351 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 25 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-39351 in the wild and no public exploit code.\n\nAffected product: DependencyTrack dependency-track. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-39351/ (Markdown: https://insights.sbomify.com/CVE-2022-39351/index.md)","id":"CVE-2022-39351","markdown":"https://insights.sbomify.com/CVE-2022-39351/index.md","name":"CVE-2022-39351","record":{"aliases":["GHSA-gh7v-4hxp-gqp4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Dependency-Track platform","requires_auth":"high_privilege","summary":"Attackers with audit log access can steal API keys logged in clear text, potentially leading to unauthorized access to the Dependency-Track platform.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dependency-track","vendor":"owasp"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in dependency-track","id":"CVE-2022-39351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"OpenFGA Authorization Bypass","id":"CVE-2022-39352"},"packages":[],"prev":{"headline":"@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details","id":"CVE-2022-39350"},"products":["dependency-track"],"published":"2022-10-25","related":[{"cvss_score":5.4,"headline":"Cross-site scripting in Dependency-Track","id":"CVE-2019-1020007","kev_date_added":null,"published":"2019-07-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["DependencyTrack"]},"summary":"Attackers with audit log access can steal API keys logged in clear text, potentially leading to unauthorized access to the Dependency-Track platform.","url":"https://insights.sbomify.com/CVE-2022-39351/"}