CVE-2020-8287: XSS
A flaw was found in nodejs. Affected versions of Node.js allow two copies of a header field in an HTTP request. The first header field is recognized while the second is ignored leading to HTTP request smuggling. The highest threat from this vulnerability is to data confidentiality and integrity.
Other sources
Affected versions of Node.js allow two copies of a header field in a 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.
Reference: https://nodejs.org/en/blog/vulnerability/january-2021-security-releases/
— Red Hat
Node.js is vulnerable to HTTP request smuggling. By sending specially crafted HTTP request headers, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.
— IBM
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.
Affected Software
Remediation
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the vulnerability ID for this Node.js vulnerability?
The vulnerability ID for this Node.js vulnerability is CVE-2020-8287.
What is the severity of CVE-2020-8287?
The severity of CVE-2020-8287 is medium.
How does CVE-2020-8287 affect Node.js?
CVE-2020-8287 allows two copies of a header field in an HTTP request, leading to HTTP request smuggling and posing a threat to data confidentiality and integrity.
Which versions of Node.js are affected by CVE-2020-8287?
Node.js versions before 10.23.1, 12.20.1, 14.15.4, and 15.5.1 are affected by CVE-2020-8287.
How can I fix CVE-2020-8287?
To fix CVE-2020-8287, upgrade to Node.js versions 10.23.1, 12.20.1, 14.15.4, or 15.5.1.