CVE-2024-7625: Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-7625?
The severity of CVE-2024-7625 is considered high due to the potential for unauthorized writes outside the allocation directory.
How do I fix CVE-2024-7625?
To fix CVE-2024-7625, upgrade to version 1.8.3, 1.7.11, or 1.6.14 of HashiCorp Nomad.
What versions of HashiCorp Nomad are affected by CVE-2024-7625?
CVE-2024-7625 affects versions from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2 of HashiCorp Nomad.
What type of vulnerability is CVE-2024-7625?
CVE-2024-7625 is a directory traversal vulnerability related to archive unpacking that can lead to file corruption or unauthorized access.
Is CVE-2024-7625 present in Nomad Enterprise?
Yes, CVE-2024-7625 is present in both HashiCorp Nomad and Nomad Enterprise within the affected versions.