CVE-2019-13623 json
In NSA Ghidra before 9.1, path traversal can occur in RestoreTask.java (from the package ghidra.app.plugin.core.archive) via an archive wit…
published 2019-07-17 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-5055
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.0%
- EPSS 5.0% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
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.
Timeline
- Published
- First public exploit (EDB-47231)
Exploit prediction
4.96% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-47231 Ghidra (Linux) 9.0.4 - .gar Arbitrary Code Execution local, 2019-08-12
- github.com https://github.com/NationalSecurityAgency/ghidra/issues/789 referenced PoC, tagged "exploit" by a source, unverified
- blog.fxiao.me http://blog.fxiao.me/ghidra/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/NationalSecurityAgency/ghidra/issues/789
exploit, third-party-advisory
-
blog.fxiao.me
/ghidra/
exploit, third-party-advisory
- packetstormsecurity.com /files/154015/Ghidra-Linux-9.0.4-Arbitrary-Code-Execution.html
- ghidra-sre.org /releaseNotes_9.1_final.html
Sources
- CVE List CVE-2019-13623
- NVD CVE-2019-13623
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.