CVE-2024-7625GHSA-25QX-VFW2-FW8RGO-2024-3073
Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.8.3, 1.6.14, 1.7.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In HashiCorp Nomad and Nomad Enterprise from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2, the archive unpacking process is vulnerable to writes outside the allocation directory during migration of allocation directories when multiple archive headers target the same file. This vulnerability, CVE-2024-7625, is fixed in Nomad 1.6.14, 1.7.11, and 1.8.3. Access or compromise of the Nomad client agent at the source allocation first is a prerequisite for leveraging this vulnerability.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- HashiCorp Nomad
From 0.6.1 · fixed in 1.8.3
- HashiCorp Nomad Enterprise
From 0.6.1 · fixed in 1.6.14
- github.com/hashicorp/nomadGo
From 0.6.1 · fixed in 1.6.14
- github.com/hashicorp/nomadGo
From 1.7.0 · fixed in 1.7.11
- github.com/hashicorp/nomadGo
From 1.8.0 · fixed in 1.8.3
- github.com/hashicorp/nomadGo
From 0.6.1 · fixed in 1.8.3