Serialize To Js Project maintains a narrowly focused JavaScript serialization library that, despite limited volume, sits within serialization and data-interchange paths in applications that depend on it. The observed vulnerabilities center on the core serialize-to-js product and its handling of untrusted input in serialization contexts. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Serialize To Js Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-5954CRITICAL 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 | Feb 10, 2017 | 9.8 | 25 | NO | NO |
CVE-2017-15871HIGH The deserialize function in serialize-to-js through 1.1.1 allows attackers to cause a denial of service via vectors involving an Immediately Invoked Function Expression "function() | Oct 24, 2017 | 7.5 | 23 | NO | NO |
CVE-2019-16772MEDIUM The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expr | Dec 7, 2019 | 6.1 | 20 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Serialize To Js Project.
Media articles that mention a CVE ID that affects a product developed by Serialize To Js Project — matched by CVE ID, not by vendor name.