CVE Vulnerabilities

CVE-2024-27983

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Published: Apr 09, 2024 | Modified: Mar 14, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

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 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.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 8 RedHat nodejs:20-8090020240422150739.a75119d5 *
Red Hat Enterprise Linux 8 RedHat nodejs:18-8090020240429131734.a75119d5 *
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support RedHat nodejs:16-8060020240515105144.ad008a3a *
Red Hat Enterprise Linux 8.6 Telecommunications Update Service RedHat nodejs:16-8060020240515105144.ad008a3a *
Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions RedHat nodejs:16-8060020240515105144.ad008a3a *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat nodejs:16-8080020240510090838.63b34585 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat nodejs:18-8080020240621122004.63b34585 *
Red Hat Enterprise Linux 9 RedHat nodejs:18-9040020240422140329.rhel9 *
Red Hat Enterprise Linux 9 RedHat nodejs:20-9040020240419140200.rhel9 *
Red Hat Enterprise Linux 9 RedHat nodejs-1:16.20.2-8.el9_4 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat nodejs-1:16.20.2-6.el9_0 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat nodejs-1:16.20.2-5.el9_2.3 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat nodejs:18-9020020240516091141.rhel9 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat rh-nodejs14-nodejs-0:14.21.3-7.el7 *
Nodejs Ubuntu esm-apps/focal *
Nodejs Ubuntu esm-apps/jammy *
Nodejs Ubuntu esm-apps/noble *
Nodejs Ubuntu focal *
Nodejs Ubuntu jammy *
Nodejs Ubuntu mantic *
Nodejs Ubuntu noble *
Nodejs Ubuntu trusty/esm *
Nodejs Ubuntu upstream *

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

References