CVE-2024-7625
Hashicorp Nomad 0.6.1 – 1.6.14
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:NSummary
CVE-2024-7625 is a medium-severity Externally Controlled Reference to a Resource in Another Sphere (CWE-610) vulnerability in Hashicorp Nomad. Its CVSS base score is 5.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2459
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so externally supplied references cannot reach resources outside the intended sphere.
Controls information flow between security domains, blocking resolution of external references to unintended spheres.
Validates information inputs, directly stopping externally controlled names or references from being accepted.
Monitors and controls boundary communications, limiting the ability of external references to reach protected resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly require input validation and reference sanitization that prevent externally-controlled resource references.
Runtime monitoring of software and data flows can detect anomalous external resource accesses that result from this weakness.
Network segmentation and access controls limit the blast radius when an external reference escapes its intended sphere.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect instances of the weakness but does not prevent it at design or coding time.
Secure development lifecycle mandates validation of all external references to prevent uncontrolled resource access.
Application security requirements explicitly call for controls against externally supplied resource identifiers.
Secure architecture principles reduce the attack surface for externally controlled references but do not prescribe specific validation rules.
Secure coding standards require input validation and canonicalization to block externally controlled resource references.
Information access restriction limits what resources can be reached, indirectly reducing impact of external references.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-610