Microsoft security update for CVE-2024-24806
🔗 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-24806. This page also shows what EchelonGraph holds for CVE-2024-24806, 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
- Azure Linux 3.0 ARM
- Azure Linux 3.0 x64
- CBL Mariner 2.0 ARM
- CBL Mariner 2.0 x64
✅ Updates Microsoft lists: 6 updates
6 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | CBL-Mariner | 1.43.0-2 |
| — | CBL-Mariner | 18.18.2-4 |
| — | CBL-Mariner | 3.28.2-6 |
| — | CBL-Mariner | 1.48.0-1 |
| — | CBL-Mariner | 20.14.0-1 |
| — | CBL-Mariner | 23.9.1-3 |
🧭 EchelonGraph on CVE-2024-24806
- 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
libuv is a multi-platform support library with a focus on asynchronous I/O. The `uv_getaddrinfo` function in `src/unix/getaddrinfo.c` (and its windows counterpart `src/win/getaddrinfo.c`), truncates hostnames to 256 characters before calling `getaddrinfo`. This behavior can be exploited to create addresses like `0x00007f000001`, which are considered valid by `getaddrinfo` and could allow an attacker to craft payloads that resolve to unintended IP addresses, bypassing developer checks. The vulnerability arises due to how the `hostname_ascii` variable (with a length of 256 bytes) is handled in `uv_getaddrinfo` and subsequently in `uv__idna_toascii`. When the hostname exceeds 256 characters, it gets truncated without a terminating null byte. As a result attackers may be able to access internal APIs or for websites (similar to MySpace) that allows users to have `username.example.com` pages. Internal services that crawl or cache these user pages can be exposed to SSRF attacks if a malicious user chooses a long vulnerable username. This issue has been addressed in release version 1.48.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-24806, 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).