Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
Summary
AIGo's HTTP/2 implementation can forward responses with malformed framing-related headers to an HTTP/1 client when acting as a reverse proxy. This can result in response smuggling if the HTTP/1 client also handles those headers too permissively. The input does not specify authentication or user-interaction requirements.
Who should check
Engineers running reverse proxies that use Go standard library net/http or net/http/internal/http2, or golang.org/x/net/http2, should check their deployments; affected versions are not specified.
What to do
- 1Consult the Go vendor advisory for affected and fixed versions.
- 2Update affected Go installations or packages according to the advisory.