GitHub Advisoryadvisory · npm
GHSA-q4v7-4rhw-9hqm Code Execution through IIFE in node-serialize
CRITICAL
Official page ↗
- Aliases
- CVE-2017-5941
- Ecosystem
- npm
- Packages
- node-serialize
- Severity
- Critical
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-502
- Reviewed
- 2020-06-16
Affected packages
• npm node-serialize: <= 0.0.4 (no fix yet)
Description
Affected versions of `node-serialize` can be abused to execute arbitrary code via an immediately invoked function expression (IIFE) if untrusted user input is passed into `unserialize()`.
Recommendation
There is no direct patch for this issue. The package author has reviewed this advisory, and provided the following recommendation:
```
To avoid the security issues, at least one of the following methods should be taken:
1. Make sure to send serialized strings internally, isolating them from potential hackers. For example, only sending the strings from backend to fronend and always using HTTPS instead of HTTP.
2. Introduce public-key cryptosystems (e.g. RSA) to ensure the strings not being tampered with.
```
Related
Alias · CVE (1)
- CVE-2017-5941 An issue was discovered in the node-serialize package 0.0.4 for Node.js. vulnerability
Weakness · CWE (1)
- CWE-502 Deserialization of Untrusted Data weakness
References
- https://nvd.nist.gov/vuln/detail/CVE-2017-5941 advisory
- https://github.com/luin/serialize/issues/4 web
- https://github.com/advisories/GHSA-q4v7-4rhw-9hqm advisory
- https://opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remote-code-execution web
- https://www.npmjs.com/advisories/311 web
- http://packetstormsecurity.com/files/161356/Node.JS-Remote-Code-Execution.html web
- http://packetstormsecurity.com/files/163222/Node.JS-Remote-Code-Execution.html web
- http://www.securityfocus.com/bid/96225 web