CVE-2024-2313
Bpftrace ≤ 0.20.2
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-2313 is a low-severity Insecure Temporary File (CWE-377) vulnerability in Bpftrace Bpftrace. Its CVSS base score is 2.8 (Low).
Operationally, ranked at the 7th 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-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-27268
Vulnerability Data
If kernel headers need to be extracted, bpftrace will attempt to load them from a temporary directory. An unprivileged attacker could use this to force bcc to load compromised linux headers. Linux distributions which provide kernel headers by default are…
more
not affected by default.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces file-system access authorizations so that temporary files cannot be read or modified by unauthorized processes.
AC-6 reduces the privileges available to processes that create or access temporary files, limiting blast radius if a file is predictable or left readable.
SC-4 directly stops unauthorized information leakage through shared resources such as world-writable temporary directories.
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 life cycle mandates secure handling of temporary files during design and coding.
A.8.26 only requires that security requirements (including resilience against injections or input validation) be identified and specified during development or acquisition; it does not itself enforce, implement or configure any mechanism that stops an insecure temporary file from being created or exploited.
Secure system architecture principles discourage insecure temporary-file patterns but do not directly address them.
Secure coding standards explicitly require safe temporary-file APIs and permissions.
Security testing can detect insecure temporary files but does not prevent their creation.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-377, a class-level weakness. Rules are authored against its narrower children: CWE-379.