Microsoft security update for CVE-2024-22017 — azl3
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-22017. This page also shows what EchelonGraph holds for CVE-2024-22017, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products4
- azl3 libuv 1.46.0-1 on Azure Linux 3.0
- azl3 libuv 1.48.0-1 on Azure Linux 3.0
- azl3 nodejs 20.10.0-2 on Azure Linux 3.0
- azl3 nodejs 20.14.0-1 on Azure Linux 3.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 20.14.0-1 |
| — | Security Update | 1.48.0-1 |
🧭 EchelonGraph on CVE-2024-22017
- EchelonGraph score
- 7.3 HIGH
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by HackerOne, the CVE Numbering Authority that assigned CVE-2024-22017, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).