CVE-2024-22017
Publication date 19 March 2024
Last updated 4 August 2025
Ubuntu priority
Cvss 3 Severity Score
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.
Why is this CVE high priority?
setting priority based on oss-security report
Status
Package | Ubuntu Release | Status |
---|---|---|
nodejs | 25.04 plucky |
Not affected
|
24.04 LTS noble |
Not affected
|
|
22.04 LTS jammy |
Not affected
|
|
20.04 LTS focal |
Not affected
|
|
18.04 LTS bionic |
Not affected
|
|
16.04 LTS xenial |
Not affected
|
|
14.04 LTS trusty |
Not affected
|
Severity score breakdown
Parameter | Value |
---|---|
Base score |
|
Attack vector | Local |
Attack complexity | Low |
Privileges required | High |
User interaction | None |
Scope | Changed |
Confidentiality | Low |
Integrity impact | High |
Availability impact | Low |
Vector | CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L |
References
Other references
- https://nodejs.org/en/blog/vulnerability/february-2024-security-releases/#setuid-does-not-drop-all-privileges-due-to-io_uring-cve-2024-22017---high
- https://www.cve.org/CVERecord?id=CVE-2024-22017
- https://www.openwall.com/lists/oss-security/2024/03/11/1
- https://github.com/nodejs/node/commit/42e659cb9d9425f76dbe9b57a437005508c0933d
- https://github.com/nodejs/node/commit/6d14352c51974f0ba1a11e9e4889e61dae9da1f4