First published: Thu Dec 08 2022(Updated: )
An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.
Credit: security@golang.org security@golang.org security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
go/golang.org/x/net | <0.4.0 | 0.4.0 |
go/golang.org/x/net/http2 | <0.4.0 | 0.4.0 |
redhat/golang | <1.19.4 | 1.19.4 |
redhat/golang | <1.18.9 | 1.18.9 |
debian/golang-1.15 | <=1.15.15-1~deb11u4 | |
debian/golang-1.19 | 1.19.8-2 | |
debian/golang-golang-x-net | <=1:0.0+git20210119.5f4716e+dfsg-4 | 1:0.7.0+dfsg-1 1:0.27.0-1 |
IBM Data Virtualization on Cloud Pak for Data | <=3.0 | |
IBM Watson Query with Cloud Pak for Data | <=2.2 | |
IBM Watson Query with Cloud Pak for Data | <=2.1 | |
IBM Watson Query with Cloud Pak for Data | <=2.0 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.8 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.7 | |
Golang | <1.18.9 | |
Golang | >=1.19.0<1.19.4 | |
Go HTTP/2 | <0.4.0 | |
Fedora | =37 | |
Fedora | =38 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-41717 is medium with a severity value of 5.3.
CVE-2022-41717 can cause excessive memory growth in a Go server accepting HTTP/2 requests.
An attacker exploiting CVE-2022-41717 can cause the server to allocate excessive memory by sending very large keys.
Versions up to and exclusive of 1.18.9 and versions between inclusive and exclusive of 1.19.0 to 1.19.4 are affected by CVE-2022-41717.
To fix CVE-2022-41717, update to Golang version 1.18.9 or 1.19.4, depending on your current version.