Node.js 6.x/8.x/9.x Buffer.fill/Buffer.alloc Parameter memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Node.js 6.x/8.x/9.x. This issue affects the function Buffer.fill/Buffer.alloc. Performing a manipulation as part of Parameter results in memory corruption. This vulnerability is identified as CVE-2018-7167. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Node.js 6.x/8.x/9.x (JavaScript Library). This affects the function Buffer.fill/Buffer.alloc. The manipulation as part of a Parameter leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on availability. The summary by CVE is:

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.

The bug was discovered 06/12/2018. The weakness was released 06/13/2018 (Website). The advisory is shared at nodejs.org. This vulnerability is uniquely identified as CVE-2018-7167 since 02/15/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 111095 (openSUSE Security Update : nodejs8 (openSUSE-2018-724)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 277331 (Fedora Security Update for nodejs (FEDORA-2018-f59d961d7b)).

Upgrading to version 10.x eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (111095) and SecurityFocus (BID 104468†). Entries connected to this vulnerability are available at VDB-117415, VDB-119538, VDB-119539 and VDB-119540. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 111095
Nessus Name: openSUSE Security Update : nodejs8 (openSUSE-2018-724)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Node.js 10.x

Timelineinfo

02/15/2018 🔍
06/12/2018 +117 days 🔍
06/12/2018 +0 days 🔍
06/13/2018 +0 days 🔍
06/13/2018 +0 days 🔍
06/14/2018 +1 days 🔍
07/13/2018 +29 days 🔍
07/16/2018 +3 days 🔍
02/19/2020 +583 days 🔍

Sourcesinfo

Advisory: nodejs.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-7167 (🔍)
GCVE (CVE): GCVE-0-2018-7167
GCVE (VulDB): GCVE-100-119541
SecurityFocus: 104468 - Node.js CVE-2018-7162 Denial of Service Vulnerability

See also: 🔍

Entryinfo

Created: 06/14/2018 10:25
Updated: 02/19/2020 12:04
Changes: 06/14/2018 10:25 (76), 02/19/2020 12:04 (5)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!