Privilege retention via stale io_uring credentials
Published Mar 19, 2024 · Updated Apr 30, 2025
Privilege retention in Node.js 20.x and 21.x allows local users to perform privileged operations after a process calls setuid(). Libuv submits io_uring operations under credentials captured before setuid(), so later asynchronous I/O retains the process's former authority. Exploitation requires a privileged Linux Node.js process that initializes io_uring before dropping its user ID, with impact limited to operations issued through that stale io_uring context.
Summary
What happened
Privilege retention in Node.js 20.x and 21.x allows local users to perform privileged operations after a process calls setuid(). Libuv submits io_uring operations under credentials captured before setuid(), so later asynchronous I/O retains the process's former authority. Exploitation requires a privileged Linux Node.js process that initializes io_uring before dropping its user ID, with impact limited to operations issued through that stale io_uring context.
The record
- CVE
- CVE-2024-22017
- Published
- Mar 19, 2024
- Updated
- Apr 30, 2025
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-250, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 19, 2024CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <10.*
- Affected versionversion=11.0 <11.*
- Affected versionversion=12.0 <12.*
- Affected versionversion=13.0 <13.*
- Affected versionversion=14.0 <14.*
- Affected versionversion=15.0 <15.*
- Affected versionversion=16.0 <16.*
- Affected versionversion=17.0 <17.*
- Affected versionversion=19.0 <19.*
- Affected versionversion=20.0 <20.11.1
- Affected versionversion=21.0 <21.6.2
- Affected versionversion=4.0 <4.*
- Affected versionversion=5.0 <5.*
- Affected versionversion=6.0 <6.*
- Affected versionversion=7.0 <7.*
- Affected versionversion=8.0 <8.*
- Affected versionversion=9.0 <9.*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo