Node.js up to 0.10.41/0.12.9/4.2.x/5.5.x HTTP Header Parser UTF-8 Encoding input validation

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.
7.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in Node.js up to 0.10.41/0.12.9/4.2.x/5.5.x and classified as critical. Affected is an unknown function of the component HTTP Header Parser. The manipulation as part of UTF-8 Encoding leads to input validation. This vulnerability is uniquely identified as CVE-2016-2216. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Node.js up to 0.10.41/0.12.9/4.2.x/5.5.x (JavaScript Library) and classified as critical. This issue affects an unknown part of the component HTTP Header Parser. The manipulation as part of a UTF-8 Encoding leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.

The weakness was disclosed 04/07/2016 by Amit Klein (Website). It is possible to read the advisory at lists.fedoraproject.org. The identification of this vulnerability is CVE-2016-2216 since 02/03/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 89508 (Fedora 23 : nodejs-0.10.42-4.fc23 (2016-3102c11757)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 168737 (OpenSuSE Security Update for Security nodejs (openSUSE-SU-2016:0604-1)).

Upgrading to version 0.10.42, 0.12.10, 4.3.0 or 5.6.0 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (89508), SecurityFocus (BID 83141†) and Vulnerability Center (SBV-58061†). The entries VDB-81704, VDB-93152 and VDB-93153 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
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: Input validation
CWE: CWE-20
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: 89508
Nessus Name: Fedora 23 : nodejs-0.10.42-4.fc23 (2016-3102c11757)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 800325
OpenVAS Name: F5 BIG-IP - Article: K23134279 - Node.js vulnerability CVE-2016-2216
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Node.js 0.10.42/0.12.10/4.3.0/5.6.0

Timelineinfo

02/03/2016 🔍
02/09/2016 +6 days 🔍
02/09/2016 +0 days 🔍
02/14/2016 +5 days 🔍
03/04/2016 +19 days 🔍
04/07/2016 +34 days 🔍
04/07/2016 +0 days 🔍
04/08/2016 +1 days 🔍
04/12/2016 +4 days 🔍
07/12/2022 +2282 days 🔍

Sourcesinfo

Advisory: FEDORA-2016-3102c11757
Researcher: Amit Klein
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-2216 (🔍)
GCVE (CVE): GCVE-0-2016-2216
GCVE (VulDB): GCVE-100-81707
SecurityFocus: 83141 - Node.js CVE-2016-2216 HTTP Response Splitting Vulnerability
Vulnerability Center: 58061 - Node.js Remote Security Bypass of HTTP Response Protection Mechanism, Medium

See also: 🔍

Entryinfo

Created: 04/08/2016 10:43
Updated: 07/12/2022 12:59
Changes: 04/08/2016 10:43 (64), 02/04/2019 11:24 (21), 07/12/2022 12:43 (3), 07/12/2022 12:52 (1), 07/12/2022 12:59 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!