CVE-2023-23916MediumMicrosoft CVSS 6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2023-23916

Published
February 24, 2023
Last Modified
—

🔗 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-23916. This page also shows what EchelonGraph holds for CVE-2023-23916, 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 products12

  • azl3 cmake 3.21.4-10 on Azure Linux 3.0
  • azl3 cmake 3.28.2-1 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-13 on CBL Mariner 2.0
  • cbl2 curl 7.88.1-1 on CBL Mariner 2.0
  • cbl2 mysql 8.0.33-1 on CBL Mariner 2.0
  • cbl2 rust 1.72.0-2 on CBL Mariner 2.0
  • cm1 cmake 3.21.4-3 on CBL Mariner 1.0
  • cm1 curl 7.88.1-1 on CBL Mariner 1.0
  • cm1 mysql 8.0.32-1 on CBL Mariner 1.0
  • cm1 rust 1.59.0-1 on CBL Mariner 1.0

✅ Updates Microsoft lists: 9 updates

9 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update2.16.1-1
—Security Update1.59.0-1
—Security Update8.0.32-1
—Security Update7.88.1-1
—Security Update3.21.4-3
—Security Update1.72.0-2
—Security Update8.0.33-1
—Security Update3.21.4-13
—Security Update3.28.2-1

🧭 EchelonGraph on CVE-2023-23916

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

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Published by HackerOne, the CVE Numbering Authority that assigned CVE-2023-23916, 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).

🔗 References (2)