CVE-2024-22017

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.

Category

7.3
CVSS
Severity: High
CVSS 3.0 •
EPSS 0.41%
Affected: NodeJS Node
Published at:
Updated at:

References

Link Tags
https://hackerone.com/reports/2170226
http://www.openwall.com/lists/oss-security/2024/03/11/1
https://security.netapp.com/advisory/ntap-20240517-0007/

Frequently Asked Questions

What is the severity of CVE-2024-22017?
CVE-2024-22017 has been scored as a high severity vulnerability.
How to fix CVE-2024-22017?
To fix CVE-2024-22017, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-22017 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-22017 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-22017?
CVE-2024-22017 affects NodeJS Node.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.