Microsoft security update for CVE-2024-1975
🔗 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-1975. This page also shows what EchelonGraph holds for CVE-2024-1975, 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 products6
- azl3 bind 9.19.21-1 on Azure Linux 3.0
- azl3 bind 9.20.0-1 on Azure Linux 3.0
- cbl2 bind 9.16.50-1 on CBL Mariner 2.0
- cbl2 bind 9.16.50-1 on CBL-Mariner 2.0
- cbl2 dhcp 4.4.3.P1-2 on CBL Mariner 2.0
- cbl2 dhcp 4.4.3.P1-2 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 3 updates
3 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 | 9.20.0-1 |
| — | Security Update | 9.16.50-1 |
| — | Security Update | 4.4.3.P1-2 |
🧭 EchelonGraph on CVE-2024-1975
- EchelonGraph score
- 7.5 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
If a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache, a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests. This issue affects BIND 9 versions 9.0.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.49-S1, and 9.18.11-S1 through 9.18.27-S1.
Published by Internet Systems Consortium (ISC), the CVE Numbering Authority that assigned CVE-2024-1975, 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).