| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Node.js up to 0.8.27/0.10.29 and classified as problematic. This issue affects some unknown processing of the component V8 Handler. Executing a manipulation can lead to memory corruption. This vulnerability is handled as CVE-2014-5256. There is not any exploit available. Applying a patch is advised to resolve this issue.
Details
A vulnerability classified as problematic was found in Node.js up to 0.8.27/0.10.29 (JavaScript Library). This vulnerability affects an unknown code of the component V8 Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability.
The weakness was released 07/31/2014 as V8 Memory Corruption and Stack Overflow (fixed in Node v0.8.28 and v0.10.30) as confirmed blog post (Website). The advisory is shared for download at blog.nodejs.org. This vulnerability was named CVE-2014-5256 since 08/15/2014. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 82395 (Mandriva Linux Security Advisory : nodejs (MDVSA-2015:142)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Mandriva Local Security Checks.
Applying a patch is able to eliminate this problem. The blog post contains the following remark:
To mitigate against deep JSON parsing you can limit the size of the string you parse against, or ban clients who trigger a RangeError for parsing JSON. There is no specific maximum size of a JSON string, though keeping the max to the size of your known message bodies is suggested. If your message bodies cannot be over 20K, there's no reason to accept 1MB bodies. For web frameworks that do automatic JSON parsing, you may need to configure the routes that accept JSON payloads to have a maximum body size.
The vulnerability is also documented in the databases at Tenable (82395), SecurityFocus (BID 69157†), Secunia (SA56216†), SecurityTracker (ID 1030811†) and Vulnerability Center (SBV-47625†). Additional details are provided at codereview.chromium.org. Entry connected to this vulnerability is available at VDB-12473. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
- 0.8.0
- 0.8.1
- 0.8.2
- 0.8.3
- 0.8.4
- 0.8.5
- 0.8.6
- 0.8.7
- 0.8.8
- 0.8.9
- 0.8.10
- 0.8.11
- 0.8.12
- 0.8.13
- 0.8.14
- 0.8.15
- 0.8.16
- 0.8.17
- 0.8.18
- 0.8.19
- 0.8.20
- 0.8.21
- 0.8.22
- 0.8.23
- 0.8.24
- 0.8.25
- 0.8.26
- 0.8.27
- 0.10.0
- 0.10.1
- 0.10.2
- 0.10.3
- 0.10.4
- 0.10.5
- 0.10.6
- 0.10.7
- 0.10.8
- 0.10.9
- 0.10.10
- 0.10.11
- 0.10.12
- 0.10.13
- 0.10.14
- 0.10.15
- 0.10.16
- 0.10.17
- 0.10.18
- 0.10.19
- 0.10.20
- 0.10.21
- 0.10.22
- 0.10.23
- 0.10.24
- 0.10.25
- 0.10.26
- 0.10.27
- 0.10.28
- 0.10.29
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 82395
Nessus Name: Mandriva Linux Security Advisory : nodejs (MDVSA-2015:142)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
07/31/2014 🔍07/31/2014 🔍
07/31/2014 🔍
08/15/2014 🔍
09/05/2014 🔍
09/05/2014 🔍
09/08/2014 🔍
12/16/2014 🔍
02/15/2022 🔍
Sources
Advisory: V8 Memory Corruption and Stack Overflow (fixed in Node v0.8.28 and v0.10.30)Status: Confirmed
Confirmation: 🔍
CVE: CVE-2014-5256 (🔍)
GCVE (CVE): GCVE-0-2014-5256
GCVE (VulDB): GCVE-100-67456
SecurityFocus: 69157 - V8 JavaScript Engine Denial of Service Vulnerability
Secunia: 56216
SecurityTracker: 1030811 - Node.js Nested JSON Processing Flaw Lets Remote Users Deny Service
Vulnerability Center: 47625 - Node.js 0.8 - 0.8.27 and 0.10 - 0.10.29 Remote DoS via Deep JSON Objects, Medium
Misc.: 🔍
See also: 🔍
Entry
Created: 09/08/2014 12:16Updated: 02/15/2022 09:41
Changes: 09/08/2014 12:16 (68), 06/15/2017 11:30 (4), 02/15/2022 09:39 (4), 02/15/2022 09:41 (1)
Complete: 🔍
Cache ID: 216:86D:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.