Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking
HashiCorp Nomad · HashiCorp Nomad Enterprise
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/nomad Go |
|
|
HashiCorp Nomad · HashiCorp Nomad Enterprise
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/nomad Go |
|
|
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.
From the CVE record · HashiCorp
HashiCorp Nomad and Nomad Enterprise can write outside an allocation directory while unpacking archives during allocation migration if multiple archive headers target the same file. Exploiting this requires prior access to or compromise of the Nomad client agent at the source allocation.
Operators of Nomad or Nomad Enterprise versions 0.6.1 through 1.6.13, 1.7.0 through 1.7.10, or 1.8.0 through 1.8.2 should check their deployments.