Skip to content
Sign in
CVE-2019-5737Not scoredCWE-400

CVE-2019-5737: Node.js vulnerability

Node.js

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

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

16.2%probability of exploitation in the next 30 days
96th percentile
050100

Higher than 96% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.

Affected products1

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

  • Node.js · Node.jsAll versions prior to 6.17.0; All versions prior to 8.15.1; All versions prior to 10.15.2; All versions prior to 11.10.1

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
Node.js
Published
March 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2019-5737 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

Updated AboutDevelopersSign in