CVE-2024-2442
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-2442 is a high-severity Path Traversal: '/../filedir' (CWE-25) vulnerability in Cisa (inferred from references). Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-27392
Vulnerability Data
Franklin Fueling System EVO 550 and EVO 5000 are vulnerable to a Path Traversal vulnerability that could allow an attacker to access sensitive files on the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes path traversal sequences such as '/../' in externally supplied filenames before they are used to construct paths.
Access enforcement ensures that even a traversed path cannot grant unauthorized access to resources outside the intended directory.
Information flow enforcement can block unauthorized data flows that would result from a successful path traversal.
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 require input validation and path sanitization that prevent traversal flaws.
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.
Secure development lifecycle mandates input validation and path sanitization that directly prevents traversal sequences.
Application security requirements explicitly call for controls against path traversal and directory escape attacks.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach a minority slice of path-traversal defects when applied to input handling and directory restrictions; most instances arise from missing or incorrect neutralization that the clause does not itself enforce.
Secure coding standards require canonicalization and neutralization of '../' sequences in path construction.
Security testing in development catches path-traversal flaws before production deployment.