CVE-2020-8265: 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.

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.

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
  53Plan
• 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

Published before and after this one in the same product

• ← EarlierCVE-2020-8277Nov 18, 2020 · A 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
• ← EarlierCVE-2018-21270Dec 3, 2020 · Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized b
  27Monitor
• Later →CVE-2020-8287Jan 6, 2021 · 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
  31Monitor

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.