{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-13623 exists.","fix":"No fix has been published for CVE-2019-13623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13623 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 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-13623 and fix it if it is affected.\n\nWhat it is: CVE-2019-13623 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-13623 exists.\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-13623/ (Markdown: https://insights.sbomify.com/CVE-2019-13623/index.md)","id":"CVE-2019-13623","markdown":"https://insights.sbomify.com/CVE-2019-13623/index.md","name":"CVE-2019-13623","record":{"aliases":["GHSA-rj42-87j6-hq79"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ghidra reverse engineering tool","requires_auth":"none","summary":"Attackers can overwrite arbitrary files via path traversal in archived analysis results, potentially leading to arbitrary code execution 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.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"In NSA Ghidra before 9.1, path traversal can occur in RestoreTask.java (from the package ghidra.app.plugin.core.archive) via an archive with an executable file that has an initial ../ in its filename. This allows attackers to overwrite arbitrary files in scenarios where an intermediate analysis result is archived for sharing with other persons. To achieve arbitrary code execution, one approach is to overwrite some critical Ghidra modules, e.g., the decompile module.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-08-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-08-12","kind":"exploitdb","ref":"47231","stars":null,"title":"Ghidra (Linux) 9.0.4 - .gar Arbitrary Code Execution"}],"tier":"weaponised"},"has_fix":false,"headline":"Path traversal in n/a","id":"CVE-2019-13623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2019-13624"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-13619"},"products":["n/a"],"published":"2019-07-17","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can overwrite arbitrary files via path traversal in archived analysis results, potentially leading to arbitrary code execution in Ghidra.","url":"https://insights.sbomify.com/CVE-2019-13623/"}