CVE-2014-5256
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.3% in the next 30 days (EPSS).
- Severity: 5.0 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.3% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Nodejs 0.8.0
- Nodejs 0.8.1
- Nodejs 0.8.2
- Nodejs 0.8.3
- Nodejs 0.8.4
- Nodejs 0.8.5
- Nodejs 0.8.6
- Nodejs 0.8.7
Attack profile CVSS 2.0 · 5.0
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2014-5256.md and follow it. Check whether this project is affected by CVE-2014-5256. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/
- https://github.com/joyent/node/commit/530af9cb8e700e7596b3ec812bad123c9fa06356
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/
- https://github.com/joyent/node/commit/530af9cb8e700e7596b3ec812bad123c9fa06356
References
- http://advisories.mageia.org/MGASA-2014-0516.html
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/
- http://secunia.com/advisories/61260
- http://www-01.ibm.com/support/docview.wss?uid=swg21684769
- http://www.mandriva.com/security/advisories?name=MDVSA-2015:142
- https://github.com/joyent/node/commit/530af9cb8e700e7596b3ec812bad123c9fa06356
- http://advisories.mageia.org/MGASA-2014-0516.html
- http://blog.nodejs.org/2014/07/31/v8-memory-corruption-stack-overflow/
- http://secunia.com/advisories/61260
- http://www-01.ibm.com/support/docview.wss?uid=swg21684769
- http://www.mandriva.com/security/advisories?name=MDVSA-2015:142
- https://github.com/joyent/node/commit/530af9cb8e700e7596b3ec812bad123c9fa06356