# CVE-2018-7167: Denial of service in Node.js

> Attackers can cause a Denial of Service in Node.js applications by triggering hangs in Buffer.fill() or Buffer.alloc() with specific parameters.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2018
- **Updated:** 8 Oct 2026
- **Also known as:** ALPINE-CVE-2018-7167, CLEANSTART-2026-JF88301, CLEANSTART-2026-WI10570, DEBIAN-CVE-2018-7167, GHSA-jr5v-587f-389p, SUSE-SU-2018:1892-1, UBUNTU-CVE-2018-7167

## What is CVE-2018-7167?

CVE-2018-7167 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-7167?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodejs6` | SUSE:Enterprise Storage 4 | All versions | 6.14.3-11.15.1 |
| `nodejs6` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 6.14.3-11.15.1 |
| `nodejs6` | SUSE:OpenStack Cloud 7 | All versions | 6.14.3-11.15.1 |
| `nodejs6` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 6.14.3-11.15.1 |

Products: Nodejs Node.js.

## How do I fix CVE-2018-7167?

Upgrade to a fixed version.

## Is CVE-2018-7167 being exploited?

There is no known exploitation of CVE-2018-7167 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7167 and fix it if it is affected.

What it is: CVE-2018-7167 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7167 in the wild and no public exploit code.

Affected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7167/ (Markdown: https://insights.sbomify.com/CVE-2018-7167/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7167
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7167
- OSV: https://osv.dev/vulnerability/CVE-2018-7167

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7167/
Summaries are generated and may contain mistakes; the official description above is the record.