Skip to content
Connect AISign inSign up free
CVE-2024-279838.2HighCWE-362

CVE-2024-27983: NodeJS vulnerability

NodeJS · Node

Vendor fix available · Affected: NodeJS · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

83.8%probability of exploitation in the next 30 days
99th percentile
050100

Higher than 99% of scored CVEs

8.2HighCVSS 3.0
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • NodeJS · Nodefrom 4.0 before 4.*; from 5.0 before 5.*; from 6.0 before 6.*; from 7.0 before 7.*; from 8.0 before 8.*; from 9.0 before 9.* and 12 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
NodeJS
Published
April 2024

Disclosed bug bounty reports about CVE-2024-27983

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

CoverageNo articles yet

No CyberSIXT article names CVE-2024-27983 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References