Back to vendor advisories
Microsoft Security Response CenterCVE-2024-28182

Reading unbounded number of HTTP/2 CONTINUATION frames to cause excessive CPU usage

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability? One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.

5.3CVSS out of 10Medium severity
Scope

What the vendor says is affected

  • cbl2 fluent-bit 3.0.6-1 on CBL Mariner 2.0
  • cbl2 rust 1.68.0-1 on CBL Mariner 2.0
  • cbl2 nodejs18 18.20.3-1 on CBL Mariner 2.0
  • cbl2 cmake 3.21.4-14 on CBL Mariner 2.0
  • azl3 fluent-bit 3.1.9-2 on Azure Linux 3.0
  • azl3 nghttp2 1.61.0-1 on Azure Linux 3.0
  • azl3 nodejs 20.14.0-1 on Azure Linux 3.0
  • azl3 cmake 3.29.6-1 on Azure Linux 3.0
  • azl3 rust 1.75.0-1 on Azure Linux 3.0
  • azl3 cmake 3.30.3-6 on Azure Linux 3.0
  • azl3 nodejs 20.10.0-2 on Azure Linux 3.0
  • azl3 nghttp2 1.59.0-1 on Azure Linux 3.0
  • cbl2 nodejs18 18.20.2-2 on CBL Mariner 2.0
  • cbl2 fluent-bit 3.0.6-2 on CBL Mariner 2.0
  • cbl2 cmake 3.21.4-17 on CBL Mariner 2.0
  • cbl2 nghttp2 1.57.0-2 on CBL-Mariner 2.0
  • cbl2 fluent-bit 3.0.6-2 on CBL-Mariner 2.0
  • cbl2 nghttp2 1.57.0-2 on CBL Mariner 2.0
  • azl3 fluent-bit 3.1.9-4 on Azure Linux 3.0
  • cbl2 cmake 3.21.4-17 on CBL-Mariner 2.0
  • cbl2 nodejs18 18.20.2-2 on CBL-Mariner 2.0

Versions the vendor lists as fixed

  • 3.0.6-1
  • 1.68.0-1
  • 18.20.3-1
  • 3.21.4-14
  • 3.1.9-2
  • 1.61.0-1
  • 20.14.0-1
  • 3.29.6-1
  • 1.75.0-1
  • 1.57.0-2
Next step

What the vendor recommends

CBL-Mariner Releases

Review the complete instructions on the vendor's site
Timeline

When this advisory changed

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.

Vulnerabilities

CVEs named in this advisory