Deserialization in Serialize-To-Js Project
CVE-2017-5954
- CVSS v3
- 9.8 Critical
- Public exploits
- None known
- EPSS
- 0.045 · 91.6th percentile
- Published
- 2017-02-10
An issue was discovered in the serialize-to-js package 0.5.0 for Node.js. Untrusted data passed into the deserialize() function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.045, 91.6th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Serialize-To-Js Project — versions 0.5.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, ossf-cve-benchmark/CVE-2017-5954). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remo… (Exploit, Third Party Advisory)
- github.com/commenthol/serialize-to-js/issues/1 (Patch, Third Party Advisory, Issue Tracking)
- www.securityfocus.com/bid/96223 (Third Party Advisory, VDB Entry, vdb-entry)