When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Datos: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Se publican tal como los indican las fuentes, en inglés.
| Fabricante | Producto | Versiones | |
|---|---|---|---|
| Go standard library | net/http | < 1.26.9 | |
| Go standard library | net/http/internal/http2 | 1.27.0-0 – < 1.27.2 | |
| golang.org/x/net | golang.org/x/net/http2 | < 0.60.0 |
Dos herramientas gratuitas, una sola defensa: el Sensor detecta a quien sondea su servidor; Shield detiene a los atacantes conocidos antes de que lleguen a su sitio.
Instálelo y su cuota diaria de API sube a 30.000 consultas, sin solicitudes.
