CVE-2024-22017

UnknownEPSS 0.89%

Last modified

CVE-2024-22017 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.89% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.89%

54.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2024-22017?
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.
How severe is CVE-2024-22017?
Severity scoring for CVE-2024-22017 is pending analysis. The EPSS model estimates a 0.89% probability of exploitation in the next 30 days.
How do I fix CVE-2024-22017?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2024-22017?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST