# CVE-2017-5941: Code Execution through IIFE in node-serialize

> Attackers can execute arbitrary code by sending malicious serialized data to the unserialize function in the node-serialize library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q4v7-4rhw-9hqm

## What is CVE-2017-5941?

CVE-2017-5941 is a critical unsafe deserialization vulnerability in n/a, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the node-serialize package 0.0.4 for Node.js. Untrusted data passed into the unserialize() function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2017-5941?

2 open source packages ship an affected version, including node-serialize. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-serialize` | npm | All versions to 0.0.4 | None |
| `node-serialize` | npm | All versions to 0.0.4 | None |

Products: Node-Serialize Project Node-Serialize.

## How do I fix CVE-2017-5941?

No fix has been published for CVE-2017-5941 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5941 being exploited?

There is no known exploitation of CVE-2017-5941 in the wild and no public exploit code.

Public exploit code:

- Exploit de reverseshell para desserialização em NodeJs (CVE-2017-5941) (github_poc): https://github.com/uartu0/nodejshell
- Node.JS - 'node-serialize' Remote Code Execution (exploitdb)
- https://github.com/Frivolous-scholar/CVE-2017-5941-NodeJS-RCE (github_poc): https://github.com/Frivolous-scholar/CVE-2017-5941-NodeJS-RCE
- Node.JS - 'node-serialize' Remote Code Execution (2) (exploitdb)
- Node.JS - 'node-serialize' Remote Code Execution (3) (exploitdb)
- https://github.com/turnernator1/Node.js-CVE-2017-5941 (github_poc): https://github.com/turnernator1/Node.js-CVE-2017-5941

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5941 and fix it if it is affected.

What it is: CVE-2017-5941 is a critical unsafe deserialization vulnerability in n/a, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5941 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-serialize (npm): affected all versions up to 0.0.4; no fix listed
- node-serialize (npm): affected all versions up to 0.0.4; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5941/ (Markdown: https://insights.sbomify.com/CVE-2017-5941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5941
- OSV: https://osv.dev/vulnerability/CVE-2017-5941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5941/
Summaries are generated and may contain mistakes; the official description above is the record.