{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17664 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17664 is a high-severity path traversal vulnerability in n/a, published on 16 Oct 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-17664 and fix it if it is affected.\n\nWhat it is: CVE-2019-17664 is a high-severity path traversal vulnerability in n/a, published on 16 Oct 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-17664 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-17664/ (Markdown: https://insights.sbomify.com/CVE-2019-17664/index.md)","id":"CVE-2019-17664","markdown":"https://insights.sbomify.com/CVE-2019-17664/index.md","name":"CVE-2019-17664","record":{"aliases":["GHSA-j2f2-77f8-cgrm"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ghidra reverse engineering tool","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious cmd.exe in the working directory when launching the Python interpreter in Ghidra.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ghidra","vendor":"nsa"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"NSA Ghidra through 9.0.4 uses a potentially untrusted search path. When executing Ghidra from a given path, the Java process working directory is set to this path. Then, when launching the Python interpreter via the \"Ghidra Codebrowser \u003e Window \u003e Python\" option, Ghidra will try to execute the cmd.exe program from this working directory.","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":"Path traversal in n/a","id":"CVE-2019-17664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2019-17665"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17663"},"products":["n/a"],"published":"2019-10-16","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-22671","kev_date_added":null,"published":"2023-01-06"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2019-16941","kev_date_added":null,"published":"2019-09-28"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2019-13625","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":8.8,"headline":"NSA Ghidra Auto-Analysis Annotation Command Execution","id":"CVE-2026-4946","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":8.7,"headline":"Ghidra 11.0 \u003c 12.1 - SQL Injection in PostgreSQL Password Change via Unescaped Username","id":"CVE-2026-49498","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.7,"headline":"Ghidra \u003c 12.1 - Authentication Bypass via Null Signature in PKIAuthenticationModule","id":"CVE-2026-52754","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.7,"headline":"Ghidra \u003c 12.1 - SQL Injection via Unescaped Filter Values in BSim Search","id":"CVE-2026-52758","kev_date_added":null,"published":"2026-06-10"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by placing a malicious cmd.exe in the working directory when launching the Python interpreter in Ghidra.","url":"https://insights.sbomify.com/CVE-2019-17664/"}