Cyber Resilience

CVE-2024-27983

Race Condition

Published
09 April 2024
Modified
17 June 2026
CVSS Score v3 8.2
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.87 99.7th percentile
Risk Priority 87 floored blend · peak EPSS

Summary

CVE-2024-27983 is a high-severity Race Condition (CWE-362) vulnerability in Fedoraproject (inferred from references). Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The vulnerability is a race condition (CWE-362) in Node.js HTTP/2 server handling that affects the nghttp2 library. When a client sends headers using HTTP/2 CONTINUATION frames and then abruptly closes the TCP connection, the Http2Session destructor can be triggered while frames are still being processed and stored in memory, leaving residual data and rendering the server unavailable.

Remote attackers with no authentication required can exploit the flaw by transmitting a small number of crafted HTTP/2 frames. Successful exploitation produces high availability impact and limited integrity impact, allowing an unauthenticated adversary to crash or hang the HTTP/2 server.

Advisories published via openwall, Fedora package lists, and NetApp reference the underlying HackerOne report and indicate that updated Node.js packages containing fixes are being distributed to address the issue.

The EPSS score stands at 0.7593 with a recorded peak of 0.7662, reflecting substantial and sustained exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with…

more

HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-53160Shared CWE-362
CVE-2024-54120Shared CWE-362
CVE-2023-52480Shared CWE-362
CVE-2023-31225Shared CWE-362
CVE-2025-38108Shared CWE-362
CVE-2026-23411Shared CWE-362
CVE-2025-38561Shared CWE-362
CVE-2024-47679Shared CWE-362
CVE-2023-42756Shared CWE-362
CVE-2025-1493Shared CWE-362

Affected Assets

Fedoraproject
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Mitigating Controls (NIST 800-53 r5) AI

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper synchronization primitives and concurrency testing that prevent race conditions.

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.

finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

prevents

Secure SDLC mandates concurrency controls and synchronization primitives that directly prevent race conditions.

prevents

Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.

prevents

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

none

Change management reduces introduction of concurrency bugs during updates, yet does not address the weakness itself.

References