Microsoft security update for CVE-2023-28321
🔗 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-2023-28321. This page also shows what EchelonGraph holds for CVE-2023-28321, 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 products5
- azl3 tensorflow 2.11.1-1 on Azure Linux 3.0
- azl3 tensorflow 2.16.1-1 on Azure Linux 3.0
- cbl2 curl 8.2.1-1 on CBL Mariner 2.0
- cbl2 mysql 8.0.34-1 on CBL Mariner 2.0
- cbl2 rust 1.72.0-2 on CBL Mariner 2.0
✅ Updates Microsoft lists: 4 updates
4 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 | 2.16.1-1 |
| — | Security Update | 1.72.0-2 |
| — | Security Update | 8.0.34-1 |
| — | Security Update | 8.2.1-1 |
🧭 EchelonGraph on CVE-2023-28321
- EchelonGraph score
- 5.9 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
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to pattern match, but the wildcard check in curl could still check for `x*`, which would match even though the IDN name most likely contained nothing even resembling an `x`.
Published by HackerOne, the CVE Numbering Authority that assigned CVE-2023-28321, 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).