Advisory

GO-2024-2687

Also known as: BIT-golang-2023-45288, CVE-2023-45288, GHSA-4v7x-pqxf-cx7m

Summary

HTTP/2 CONTINUATION flood in net/http

Details

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

The fix sets a limit on the amount of excess header frames we will process before closing a connection.

Severity

Not rated by the source.

Dates

Published
2024-04-03 21:12 UTC
Modified
2026-02-04 04:09 UTC

Affected packages and fixes

stdlib

Go · All systems

Affected

  • introduced 0, fixed 1.21.9, introduced 1.22.0-0, fixed 1.22.2 (semver)

Fixed versions

1.21.9, 1.22.2

Fix

The export has no generic command for this ecosystem.

golang.org/x/net

Go · All systems

Affected

  • introduced 0, fixed 0.23.0 (semver)

Fixed versions

0.23.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Go Vulnerability Database · CC BY 4.0

Sources & licences