HighCVE-2024-27983

    Node: Race Condition (CVE-2024-27983)

    Published Sources: Debian, CVE.org, OSV, BSI

    What is affected, what to do

    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.

    Update Node to version 18.20.1, Node to version 20.12.1, Node to version 21.7.2.

    Affected
    • Node gte 4.0..*
    • Node gte 5.0..*
    • Node gte 6.0..*
    • Node gte 7.0..*
    • Node gte 8.0..*
    • Node gte 9.0..*
    • Node gte 10.0..*
    • Node gte 11.0..*
    • Node gte 12.0..*
    • Node gte 13.0..*
    • Node gte 14.0..*
    • Node gte 15.0..*
    • Node gte 16.0..*
    • Node gte 17.0..*
    • Node lt 18.0..18.20.1
    • Node gte 19.0..*
    • Node lt 20.0..20.12.1
    • Node lt 21.0..21.7.2
    Fixed in
    • Node 18.20.1
    • Node 20.12.1
    • Node 21.7.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.2

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Debian, CVE.org, OSV, BSI

    87.2 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.75

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    125.50 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.2 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    87.2 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.75
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 9 April 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-362

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: Debian Security Advisories, NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities), BSI CSAF, BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    NodeJSNode
    • 20.0 – < 20.12.1
    • ≥ 4.0
    • ≥ 12.0
    • ≥ 16.0
    • 18.0 – < 18.20.1
    • ≥ 8.0
    • ≥ 5.0
    • ≥ 11.0
    • ≥ 9.0
    • ≥ 7.0
    • ≥ 6.0
    • ≥ 15.0
    • ≥ 13.0
    • ≥ 17.0
    • ≥ 14.0
    • 21.0 – < 21.7.2
    • ≥ 19.0
    • ≥ 10.0
    • 20.12.1
    • —
    • —
    • —
    • 18.20.1
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 21.7.2
    • —
    • —
    OracleJD Edwards
    • < 9.2.9.0
    • < 9.2.9.2
    • 9.2.9.0
    • 9.2.9.2
    Distribution and container packages (2)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnaminode-min
    • 21.0.0
    • 19.0.0
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebiannodejsbookworm

    Weakness classes (CWE)

    • CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

      Class

      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.

      Entry at MITRE CWE-362

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-27983
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-27983"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-27983.svg?lang=en" alt="CVE-2024-27983 – NEOSEC Intel" height="20"></a>