Skip to content
Noroxi
CVE-2020-8287· NVD / CVE Program· CNA hackerone

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-E

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

MediumCVSS 6.5 · v3.1—Proof of concept Fix available
Published
Jan 6, 2021
Updated
Jun 16, 2026
EPSS
16.3% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 16.3%

Affected systems

VendorProduct
nodejsnode.js
debiandebian linux
fedoraprojectfedora
oraclegraalvm
siemenssinec infrastructure network services

Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js10.0.0 and later · before 10.23.1
  • nodejs node.js12.0.0 and later · before 12.20.1
  • nodejs node.js14.0.0 and later · before 14.15.4
  • nodejs node.js15.0.0 and later · before 15.5.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • NodeJS Node

    • 4.0 and later · before 4.*affected · semver
    • 5.0 and later · before 5.*affected · semver
    • 6.0 and later · before 6.*affected · semver
    • 7.0 and later · before 7.*affected · semver
    • 8.0 and later · before 8.*affected · semver
    • 9.0 and later · before 9.*affected · semver
    • 10.0 and later · before 10.23.1affected · semver
    • 11.0 and later · before 11.*affected · semver
    • 12.0 and later · before 12.20.1affected · semver
    • 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2047+b07ac28e1.18.3-1.module_el8.3.0+2047+b07ac28e
AlmaLinux:8nodejs-nodemonbefore 2.0.3-1.module_el8.4.0+2521+c668cc9f2.0.3-1.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2023+d2377ea31.18.3-1.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.5.0+254+b4526b1623-3.module_el8.5.0+254+b4526b16
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2224+b07ac28e17-3.module_el8.4.0+2224+b07ac28e
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2521+c668cc9f17-3.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.3.0+2023+d2377ea317-3.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.4.0+2522+3bd4276223-3.module_el8.4.0+2522+3bd42762
Alpine:v3.11nodejsbefore 12.20.1-r012.20.1-r0
Alpine:v3.13nodejsbefore 14.15.4-r014.15.4-r0
Debian:10http-parserbefore 2.8.1-1+deb10u32.8.1-1+deb10u3
Debian:10nodejsbefore 10.23.1~dfsg-1~deb10u110.23.1~dfsg-1~deb10u1
Debian:12http-parserbefore 2.9.4-52.9.4-5
Debian:12nodejsbefore 12.20.1~dfsg-112.20.1~dfsg-1
openSUSE:Leap 15.1nodejs10before 10.23.1-lp151.2.15.110.23.1-lp151.2.15.1
openSUSE:Leap 15.2nodejs10before 10.23.1-lp152.2.9.110.23.1-lp152.2.9.1
openSUSE:Leap 15.2nodejs12before 12.20.1-lp152.3.9.112.20.1-lp152.3.9.1
openSUSE:Leap 15.2nodejs14before 14.15.4-lp152.5.114.15.4-lp152.5.1
openSUSE:Leap 15.2nodejs8before 8.17.0-lp152.3.8.18.17.0-lp152.3.8.1
openSUSE:Tumbleweednodejs14before 14.17.5-1.214.17.5-1.2
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:12.20.1-1.module+el8.3.0+9503+19cb079c1:12.20.1-1.module+el8.3.0+9503+19cb079c
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:14.15.4-2.module+el8.3.0+9635+ffdf83811:14.15.4-2.module+el8.3.0+9635+ffdf8381
Red Hat:enterprise_linux:8::appstreamnodejs-debuginfobefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97

+55

Other highest-scoring records for the same primary product.

  • CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
    56Plan
  • CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
    52Plan
  • CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
    50Plan
  • CVE-2021-22931Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation
    46Plan
  • CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi
    46Plan
  • CVE-2017-14849Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p
    46Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NodeJS Node10.23.1Vendor (CNA)
NodeJS Node11.*Vendor (CNA)
NodeJS Node12.20.1Vendor (CNA)
NodeJS Node13.*Vendor (CNA)
NodeJS Node14.15.4Vendor (CNA)
NodeJS Node15.5.1Vendor (CNA)
NodeJS Node4.*Vendor (CNA)
NodeJS Node5.*Vendor (CNA)
NodeJS Node6.*Vendor (CNA)
NodeJS Node7.*Vendor (CNA)
NodeJS Node8.*Vendor (CNA)
NodeJS Node9.*Vendor (CNA)
almalinux:nodejs-nodemon1.18.3-1.module_el8.3.0+2023+d2377ea3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8Package registry (OSV)
alpine:nodejs12.20.1-r0 · Alpine:v3.11Package registry (OSV)
debian:http-parser2.9.4-5 · Debian:12Package registry (OSV)
debian:nodejs12.20.1~dfsg-1 · Debian:12Package registry (OSV)
opensuse:nodejs1010.23.1-lp152.2.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs1212.20.1-lp152.3.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs1414.15.4-lp152.5.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs88.17.0-lp152.3.8.1 · openSUSE:Leap 15.2Package registry (OSV)
red hat:rh-nodejs10-nodejs0:10.23.1-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs0:12.20.1-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-debuginfo0:12.20.1-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-devel0:12.20.1-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-docs0:12.20.1-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-nodemon0:2.0.3-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-npm0:6.14.10-12.20.1.1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs0:14.15.4-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs-debuginfo0:14.15.4-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)

+9

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:22021-01-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-2 d
  2. Published
  3. TodaySep 30, 2026+2093 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records