CVE-2024-22017 Privilege escalation in Node
Attackers can retain privileged operations after dropping privileges via setuid() if libuv io_uring was initialized earlier, leading to privilege escalation in Node.js applications.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-22017?
CVE-2024-22017 is a high-severity vulnerability in NodeJS Node, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
setuid() does not affect libuv's internal io_uring operations if initialized before the call to setuid(). This allows the process to perform privileged operations despite presumably having dropped such privileges through a call to setuid(). This vulnerability affects all users using version greater or equal than Node.js 18.18.0, Node.js 20.4.0 and Node.js 21.
Weakness: CWE-250
Which versions are affected by CVE-2024-22017?
2 open source packages ship an affected version, including node and node-min.
| Package | Affected | Fixed in |
|---|---|---|
node Bitnami | From 20.0.0 | 20.11.1, 21.6.2 |
node-min Bitnami | From 20.0.0 | 20.11.1, 21.6.2 |
Linux distribution packages (1)
nodejs-electron openSUSE:Tumbleweed | All versions | 29.4.0-1.1 |
How do I fix CVE-2024-22017?
Upgrade node to a fixed version for your release line: 20.11.1 or 21.6.2.
Is CVE-2024-22017 being exploited?
There is no known exploitation of CVE-2024-22017 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as AZL-35886, AZL-35899, BELL-CVE-2024-22017, BIT-node-2024-22017, BIT-node-min-2024-22017, GHSA-vr4q-vx84-9g5x and 1 more.