Microsoft security update for CVE-2022-43551
🔗 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-2022-43551. This page also shows what EchelonGraph holds for CVE-2022-43551, 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 products7
- azl3 cmake 3.21.4-10 on Azure Linux 3.0
- azl3 tensorflow 2.11.1-1 on Azure Linux 3.0
- azl3 tensorflow 2.16.1-1 on Azure Linux 3.0
- cbl2 cmake 3.21.4-3 on CBL Mariner 2.0
- cbl2 curl 7.86.0-2 on CBL Mariner 2.0
- cm1 cmake 3.21.4-3 on CBL Mariner 1.0
- cm1 curl 7.86.0-2 on CBL Mariner 1.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 | 3.21.4-3 |
| — | Security Update | 7.86.0-2 |
| — | Security Update | 3.21.4-10 |
🧭 EchelonGraph on CVE-2022-43551
- 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
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
Published by HackerOne, the CVE Numbering Authority that assigned CVE-2022-43551, 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).