OESA-2021-1058 (CVE-2020-8287)
Vulnerability from osv_openeuler – Published: 2021-03-05 11:04 – Updated: 2026-08-06 11:04 – Source websiteNode.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Security Fix(es):
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.(CVE-2020-8287)
Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits.(CVE-2020-8265)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"nodejs-libs-10.21.0-4.oe1.aarch64.rpm",
"nodejs-10.21.0-4.oe1.aarch64.rpm",
"nodejs-devel-10.21.0-4.oe1.aarch64.rpm",
"nodejs-debuginfo-10.21.0-4.oe1.aarch64.rpm",
"nodejs-full-i18n-10.21.0-4.oe1.aarch64.rpm",
"nodejs-debugsource-10.21.0-4.oe1.aarch64.rpm",
"npm-6.14.4-1.10.21.0.4.oe1.oe1.aarch64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.4.oe1.oe1.aarch64.rpm",
"nodejs-libs-10.21.0-5.oe1.aarch64.rpm",
"nodejs-10.21.0-5.oe1.aarch64.rpm",
"nodejs-devel-10.21.0-5.oe1.aarch64.rpm",
"nodejs-debuginfo-10.21.0-5.oe1.aarch64.rpm",
"nodejs-full-i18n-10.21.0-5.oe1.aarch64.rpm",
"nodejs-debugsource-10.21.0-5.oe1.aarch64.rpm",
"npm-6.14.4-1.10.21.0.5.oe1.oe1.aarch64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.5.oe1.oe1.aarch64.rpm"
],
"noarch": [
"nodejs-docs-10.21.0-4.oe1.noarch.rpm",
"nodejs-docs-10.21.0-5.oe1.noarch.rpm"
],
"src": [
"nodejs-10.21.0-4.oe1.src.rpm",
"nodejs-10.21.0-5.oe1.src.rpm"
],
"x86_64": [
"nodejs-devel-10.21.0-4.oe1.x86_64.rpm",
"npm-6.14.4-1.10.21.0.4.oe1.oe1.x86_64.rpm",
"nodejs-10.21.0-4.oe1.x86_64.rpm",
"nodejs-libs-10.21.0-4.oe1.x86_64.rpm",
"nodejs-debugsource-10.21.0-4.oe1.x86_64.rpm",
"nodejs-debuginfo-10.21.0-4.oe1.x86_64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.4.oe1.oe1.x86_64.rpm",
"nodejs-full-i18n-10.21.0-4.oe1.x86_64.rpm",
"nodejs-devel-10.21.0-5.oe1.x86_64.rpm",
"npm-6.14.4-1.10.21.0.5.oe1.oe1.x86_64.rpm",
"nodejs-10.21.0-5.oe1.x86_64.rpm",
"nodejs-libs-10.21.0-5.oe1.x86_64.rpm",
"nodejs-debugsource-10.21.0-5.oe1.x86_64.rpm",
"nodejs-debuginfo-10.21.0-5.oe1.x86_64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.5.oe1.oe1.x86_64.rpm",
"nodejs-full-i18n-10.21.0-5.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS",
"name": "nodejs",
"purl": "pkg:rpm/openEuler/nodejs\u0026distro=openEuler-20.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "10.21.0-5.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"nodejs-libs-10.21.0-5.oe1.aarch64.rpm",
"nodejs-10.21.0-5.oe1.aarch64.rpm",
"nodejs-devel-10.21.0-5.oe1.aarch64.rpm",
"nodejs-debuginfo-10.21.0-5.oe1.aarch64.rpm",
"nodejs-full-i18n-10.21.0-5.oe1.aarch64.rpm",
"nodejs-debugsource-10.21.0-5.oe1.aarch64.rpm",
"npm-6.14.4-1.10.21.0.5.oe1.oe1.aarch64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.5.oe1.oe1.aarch64.rpm"
],
"noarch": [
"nodejs-docs-10.21.0-5.oe1.noarch.rpm"
],
"src": [
"nodejs-10.21.0-5.oe1.src.rpm"
],
"x86_64": [
"nodejs-devel-10.21.0-5.oe1.x86_64.rpm",
"npm-6.14.4-1.10.21.0.5.oe1.oe1.x86_64.rpm",
"nodejs-10.21.0-5.oe1.x86_64.rpm",
"nodejs-libs-10.21.0-5.oe1.x86_64.rpm",
"nodejs-debugsource-10.21.0-5.oe1.x86_64.rpm",
"nodejs-debuginfo-10.21.0-5.oe1.x86_64.rpm",
"v8-devel-6.8.275.32-1.10.21.0.5.oe1.oe1.x86_64.rpm",
"nodejs-full-i18n-10.21.0-5.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "nodejs",
"purl": "pkg:rpm/openEuler/nodejs\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "10.21.0-5.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Node.js is a platform built on Chrome\u0027s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.\r\n\r\nSecurity Fix(es):\r\n\r\nNode.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.(CVE-2020-8287)\r\n\r\nNode.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits.(CVE-2020-8265)",
"id": "OESA-2021-1058",
"modified": "2026-08-06T11:04:17Z",
"published": "2021-03-05T11:04:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8287"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8265"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "nodejs security update",
"upstream": [
"CVE-2020-8287",
"CVE-2020-8265"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.