CVE-2024-7400
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-7400 is a high-severity Insecure Operation on Windows Junction / Mount Point (CWE-1386) vulnerability in Eset (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Direct Volume Access (T1006); ranked at the 13th 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-48331
Vulnerability Data
The vulnerability potentially allowed an attacker to misuse ESET’s file operations during the removal of a detected file on the Windows operating system to delete files without having proper permissions to do so.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.3
Mitigating Controls (NIST 800-53 r5) AI
Enforcing authorizations on file/directory opens structurally blocks access via junctions that escape the intended scope.
Information-flow rules that validate the final target of a name prevent unintended data access through mount points or junctions.
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 SDLC practices directly prevent improper junction/mount-point handling during design and coding.
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 junction/mount-point weaknesses before release.
Secure development lifecycle can mandate junction/mount-point validation during design and coding.
Application security requirements can explicitly require protection against Windows reparse-point attacks.
Secure system architecture principles include canonicalization and path-traversal defenses that mitigate junction attacks.
Secure coding standards directly address safe file/directory handling to prevent insecure junction operations.
Information access restriction reduces exposure but does not prevent the technical flaw itself.