{"answers":{"affected":"2 open source packages ship an affected version, including snyk-broker. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7654 in the wild and no public exploit code.","fix":"Upgrade snyk-broker to 4.73.1 or later.","what":"CVE-2020-7654 is a high-severity vulnerability in snyk-broker, published on 29 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7654 and fix it if it is affected.\n\nWhat it is: CVE-2020-7654 is a high-severity vulnerability in snyk-broker, published on 29 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7654 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- snyk-broker (npm): affected all versions; fixed in 4.73.1\n- snyk-broker (npm): affected all versions; fixed in 4.73.1\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-2020-7654/ (Markdown: https://insights.sbomify.com/CVE-2020-7654/index.md)","id":"CVE-2020-7654","markdown":"https://insights.sbomify.com/CVE-2020-7654/index.md","name":"CVE-2020-7654","record":{"aliases":["GHSA-mgh5-4h95-qj4p","SNYK-JS-SNYKBROKER-570613"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Snyk Broker","requires_auth":"none","summary":"Snyk Broker logs private keys when debug logging is enabled, exposing sensitive credentials to anyone with log access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"broker","vendor":"synk"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information Exposure in Snyk Broker","id":"CVE-2020-7654","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"HTTP Request Smuggling in netius","id":"CVE-2020-7655"},"packages":[{"ecosystem":"npm","fixed":["4.73.1"],"introduced":["0"],"last_affected":[],"package":"snyk-broker","purl":null,"source":"GHSA-mgh5-4h95-qj4p"},{"ecosystem":"npm","fixed":["4.73.1"],"introduced":["0"],"last_affected":[],"package":"snyk-broker","purl":"pkg:npm/snyk-broker","source":"GHSA-mgh5-4h95-qj4p"}],"prev":{"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7653"},"products":["snyk-broker"],"published":"2020-05-29","related":[{"cvss_score":6.5,"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7648","kev_date_added":null,"published":"2020-05-29"},{"cvss_score":6.5,"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7650","kev_date_added":null,"published":"2020-05-29"},{"cvss_score":6.5,"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7652","kev_date_added":null,"published":"2020-05-29"},{"cvss_score":6.5,"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7653","kev_date_added":null,"published":"2020-05-29"},{"cvss_score":4.3,"headline":"Arbitrary File Read in Snyk Broker","id":"CVE-2020-7651","kev_date_added":null,"published":"2020-05-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Snyk Broker logs private keys when debug logging is enabled, exposing sensitive credentials to anyone with log access.","url":"https://insights.sbomify.com/CVE-2020-7654/"}