Denial of Service Vulnerability in Node.js

nodejs Updated 02 Oct 2025

Summary

13/06/2018
N/A
Yes i
High
7.5

CVE-2018-7167: Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. Affects nodejs across 2 version ranges.

< 8.11.3-r0 < 8c9f0d0fb4c3b8625c4b7a2ec654655fe9a67c92

Fixed in 8.11.3-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Node.js is a popular JavaScript runtime built on Chrome's V8 JavaScript engine. It allows developers to build scalable and high-performance applications. However, a vulnerability has been discovered in Node.js that can lead to a Denial of Service (DoS) attack.

Vulnerability Detail

The vulnerability, identified as CVE-2018-7167, arises when calling Buffer.fill() or Buffer.alloc() with certain parameters. This can cause the application to hang indefinitely, resulting in a DoS condition. Attackers can exploit this vulnerability to disrupt the availability of affected Node.js applications. The vulnerability affects all versions of Node.js 6.x, 8.x, and 9.x, but not Node.js 10.x.

How To Fix

Minimum fixed version

8.11.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade nodejs

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the fixed version of Node.js.

Conclusion

The Denial of Service vulnerability in Node.js can be mitigated by upgrading to the fixed version. It is important to keep your Node.js installations up to date to ensure the security and stability of your applications. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for nodejs →

Share this vulnerability

FAQ

The vulnerability can lead to a Denial of Service (DoS) attack, causing the affected Node.js application to become unresponsive or crash.

All versions of Node.js 6.x, 8.x, and 9.x are vulnerable. Node.js 10.x is not affected.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will provide real-time alerts for open-source vulnerabilities.

Yes, the fix for this vulnerability is available in Node.js version 8.11.3-r0 or later. It is recommended to upgrade to the fixed version.

There are no specific workarounds mentioned for this vulnerability. Upgrading to the fixed version of Node.js is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for nodejs.

How To Fix

Minimum fixed version

8.11.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade nodejs

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback