CVE-2024-23454
Apache Hadoop ≤ 3.4.0
Raw vector
CVSS:3.1/AV:L/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-23454 is a medium-severity Creation of Temporary File With Insecure Permissions (CWE-378) vulnerability in Apache Hadoop. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked at the 33th 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-6 (Least Privilege) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2780
Vulnerability Data
Apache Hadoop’s RunJar.run() does not set permissions for temporary directory by default. If sensitive data will be present in this file, all the other local users may be able to view the content. This is because, on unix-like systems, the…
more
system temporary directory is shared between all local users. As such, files written in this directory, without setting the correct posix permissions explicitly, may be viewable by all other local users.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-6 limits privileges granted to processes creating or accessing temporary files, reducing blast radius of insecure permissions.
SC-4 directly stops unauthorized information transfer through shared resources such as temporary files created with weak permissions.
AC-3 enforces access authorizations on system resources including files, structurally stopping insecure temporary file permissions from being exploitable.
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 proper temporary-file creation and permission handling.
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 SDLC mandates secure handling of temporary files and permissions.
A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent insecure temporary file permissions from being exploitable.
A.8.27 mandates security-by-design principles (least privilege, default-deny, hardening, secure-by-default) plus design reviews that can catch and block insecure temporary-file permissions during architecture and engineering, but this is only one minority slice of CWE-378's surface (many instances arise from ad-hoc runtime file creation outside any reviewed design or outsourced development).
Secure coding standards directly prohibit insecure temporary file creation and permissions.
Security testing can detect insecure temporary files but does not prevent their creation.