Loading vulnerability…
CVE-2024-22017 is an improper privilege-management vulnerability in Node.js arising from libuv internal io_uring operations on Linux. If libuv initializes io_uring while the process has elevated credentials, a subsequent call to setuid() does not affect those already initialized operations. The process can therefore continue to perform io_uring-backed operations using privileges that the application intended to drop. Affected releases include Node.js 18.18.0 and later in the 18.x line, 20.4.0 and later in the 20.x line, and 21.x prior to the vendor fixes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2024-22017, targeting Node.js. The main file, 'a.js', is a JavaScript script that sets the environment variable 'UV_USE_IO_URING', changes the process UID to 400, and then spawns a 'cmd.exe' process to execute the 'whoami' command. The output of the command is printed to the console, demonstrating the user context under which the command is run. The exploit is local and requires the ability to run Node.js scripts with sufficient privileges. The repository structure is minimal, consisting of a README and the exploit script. No network endpoints or remote attack vectors are present; the only fingerprintable endpoint is the use of 'cmd.exe' as the spawned process.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.