CVE-2018-7167: The Node.js Project Node.js vulnerability

CVE-2018-7167: Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Den...

Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of Node.js 6.x (LTS "Boron"), 8.x (LTS "Carbon"), and 9.x are vulnerable. All versions of Node.js 10.x (Current) are NOT vulnerable.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 02:00 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2018-7167 can make affected Node.js applications hang when specific buffer operations are called. The business impact is availability: a reachable service could stop responding if vulnerable code paths are exposed. The provided sources identify Node.js 6.x, 8.x, and 9.x as vulnerable; Node.js 10.x is stated not vulnerable. Exposure is most likely in legacy services, containers, serverless builds, or packaged applications running Node.js 6.x, 8.x, or 9.x. Risk is higher when external input can influence buffer allocation or fill behavior. Node.js 10.x is listed as not vulnerable. Treat this as a legacy-runtime availability risk. It is not KEV-listed and no active exploitation is cited, but internet-facing or business-critical services on Node.js 6.x, 8.x, or 9.x should be remediated promptly because a hang can cause service disruption. Mitigation focus: Upgrade affected Node.js 6.x, 8.x, and 9.x runtimes to a fixed supported release.; Use the Node.js June 2018 security advisory for vendor-specific fixed release guidance.; For Gentoo systems, follow GLSA-202003-48 package remediation guidance..

Prepared: Jun 7, 2026, 13:21 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-7167 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 13, 2018, 16:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://nodejs.org/en/blog/vulnerability/june-2018-security-releases/CVE reference · x_refsource_CONFIRM
GLSA-202003-48CVE reference · vendor-advisory, x_refsource_GENTOO

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

The Node.js ProjectNode.js6.x+, 8.x+, 9.x+, 10.x+Listed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.