Microsoft security update for CVE-2024-9681
🔗 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-9681. This page also shows what EchelonGraph holds for CVE-2024-9681, 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 products17
- azl3 cmake 3.30.3-4 on Azure Linux 3.0
- azl3 cmake 3.30.3-6 on Azure Linux 3.0
- azl3 curl 8.8.0-4 on Azure Linux 3.0
- azl3 mysql 8.0.40-5 on Azure Linux 3.0
- azl3 mysql 8.0.40-6 on Azure Linux 3.0
- azl3 tensorflow 2.16.1-7 on Azure Linux 3.0
- cbl2 cmake 3.21.4-16 on CBL Mariner 2.0
- cbl2 cmake 3.21.4-17 on CBL Mariner 2.0
- cbl2 cmake 3.21.4-17 on CBL-Mariner 2.0
- cbl2 curl 8.8.0-5 on CBL Mariner 2.0
- cbl2 curl 8.8.0-6 on CBL Mariner 2.0
- cbl2 curl 8.8.0-6 on CBL-Mariner 2.0
- cbl2 mysql 8.0.40-3 on CBL Mariner 2.0
- cbl2 mysql 8.0.40-4 on CBL Mariner 2.0
- cbl2 mysql 8.0.40-4 on CBL-Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 8 updates
8 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 | 1.72.0-10 |
| — | Security Update | 8.0.40-3 |
| — | Security Update | 3.21.4-16 |
| — | Security Update | 8.8.0-5 |
| — | Security Update | 2.16.1-7 |
| — | Security Update | 8.0.40-5 |
| — | Security Update | 3.30.3-4 |
| — | Security Update | 8.8.0-4 |
🧭 EchelonGraph on CVE-2024-9681
- EchelonGraph score
- 6.5 MEDIUM
- 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
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.
Published by curl, the CVE Numbering Authority that assigned CVE-2024-9681, 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).