Advisory

GO-2023-2102

Also known as: BIT-golang-2023-39325, CVE-2023-39325, GHSA-4374-p667-p6c8

Summary

HTTP/2 rapid reset can cause excessive work in net/http

Details

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

Severity

Not rated by the source.

Dates

Published
2023-10-11 16:49 UTC
Modified
2026-11-13 19:12 UTC

Affected packages and fixes

stdlib

Go · All systems

Affected

  • introduced 0, fixed 1.20.10, introduced 1.21.0-0, fixed 1.21.3 (semver)

Fixed versions

1.20.10, 1.21.3

Fix

The export has no generic command for this ecosystem.

golang.org/x/net

Go · All systems

Affected

  • introduced 0, fixed 0.17.0 (semver)

Fixed versions

0.17.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