7.5
Élevée
CVE-2023-24534 HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading…
Description
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| net/textproto 1.20 | 1.20.0-0 → < 1.20.3 | 1.20.3 |
| net/textproto 1.19 | premières → < 1.19.8 | 1.19.8 |
Références
- go.dev go.dev
- go.dev go.dev
- groups.google.com groups.google.com
- pkg.go.dev pkg.go.dev
- security.netapp.com security.netapp.com
- security.gentoo.org security.gentoo.org
Chronologie
- Publiée
- Dernière modification
Autres CVE de net/textproto
Les 6 CVE de net/textproto →
CVE-2026-94440
Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit…
7.5
Élevée
CVE-2026-42507
When returning errors, functions in the net/textproto package would include its input as part of the error
5.3
Moyenne
CVE-2025-61724
The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines
5.3
Moyenne
CVE-2023-45290
When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue,…
6.5
Moyenne