CVE-2014-5256
Last modified
CVE-2014-5256 is a vulnerability of currently unknown severity. Node.js 0.8 before 0.8.28 and 0.10 before 0.10.30 does not consider the possibility of recursive processing that triggers V8 garbage collection in conjunction with a V8 interrupt, which allows remote attackers to cause a denial of service (memory corruption and application crash) via deep JSON objects whose parsing lets this interrupt mask an overflow of the program stack.. EPSS estimates a 3.26% chance of exploitation in the next 30 days.
Description
Node.js 0.8 before 0.8.28 and 0.10 before 0.10.30 does not consider the possibility of recursive processing that triggers V8 garbage collection in conjunction with a V8 interrupt, which allows remote attackers to cause a denial of service (memory corruption and application crash) via deep JSON objects whose parsing lets this interrupt mask an overflow of the program stack.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Nodejs | 0.8.0 |
| Nodejs | Nodejs | 0.8.1 |
| Nodejs | Nodejs | 0.8.2 |
| Nodejs | Nodejs | 0.8.3 |
| Nodejs | Nodejs | 0.8.4 |
| Nodejs | Nodejs | 0.8.5 |
| Nodejs | Nodejs | 0.8.6 |
| Nodejs | Nodejs | 0.8.7 |
| Nodejs | Nodejs | 0.8.8 |
| Nodejs | Nodejs | 0.8.9 |
| Nodejs | Nodejs | 0.8.10 |
| Nodejs | Nodejs | 0.8.11 |
| Nodejs | Nodejs | 0.8.12 |
| Nodejs | Nodejs | 0.8.13 |
| Nodejs | Nodejs | 0.8.14 |
| Nodejs | Nodejs | 0.8.15 |
| Nodejs | Nodejs | 0.8.16 |
| Nodejs | Nodejs | 0.8.17 |
| Nodejs | Nodejs | 0.8.18 |
| Nodejs | Nodejs | 0.8.19 |
| Nodejs | Nodejs | 0.8.20 |
| Nodejs | Nodejs | 0.8.21 |
| Nodejs | Nodejs | 0.8.22 |
| Nodejs | Nodejs | 0.8.23 |
| Nodejs | Nodejs | 0.8.24 |
| Nodejs | Nodejs | 0.8.25 |
| Nodejs | Nodejs | 0.8.26 |
| Nodejs | Nodejs | 0.8.27 |
| Nodejs | Nodejs | 0.10.0 |
| Nodejs | Nodejs | 0.10.1 |
| Nodejs | Nodejs | 0.10.2 |
| Nodejs | Nodejs | 0.10.3 |
| Nodejs | Nodejs | 0.10.4 |
| Nodejs | Nodejs | 0.10.5 |
| Nodejs | Nodejs | 0.10.6 |
| Nodejs | Nodejs | 0.10.7 |
| Nodejs | Nodejs | 0.10.8 |
| Nodejs | Nodejs | 0.10.9 |
| Nodejs | Nodejs | 0.10.10 |
| Nodejs | Nodejs | 0.10.11 |
| Nodejs | Nodejs | 0.10.12 |
| Nodejs | Nodejs | 0.10.13 |
| Nodejs | Nodejs | 0.10.14 |
| Nodejs | Nodejs | 0.10.15 |
| Nodejs | Nodejs | 0.10.16 |
| Nodejs | Nodejs | 0.10.17 |
| Nodejs | Nodejs | 0.10.18 |
| Nodejs | Nodejs | 0.10.19 |
| Nodejs | Nodejs | 0.10.20 |
| Nodejs | Nodejs | 0.10.21 |
Showing 50 of 58 affected configurations. See NVD for the full list.
References
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/Patch, Vendor Advisory
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2014-5256?
How severe is CVE-2014-5256?
How do I fix CVE-2014-5256?
Are you affected by CVE-2014-5256?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
