Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Excessive memory growth in net/http and golang.org/x/net/http2

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 5.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by golang.org/x/net/http2 0.4.0Fixed by golang.org/x/net 0.4.0osv · severity unknownFixed by stdlib 1.18.9Fixed by stdlib 1.19.4Fixed by golang.org/x/net 0.4.0KEV status unknown

cve-program · CVE-2022-41717

Published

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.

Read the publisher's advisory

euvd · EUVD-2022-7776

Published

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.

Read the publisher's advisory

nvd · CVE-2022-41717

Published

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.

Read the publisher's advisory

osv · GHSA-xrjj-mj9h-534m

Published

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.

Read the publisher's advisory

osv · GO-2022-1144

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2022-41717 · CVE overview and exploitation status

EUVD-2022-7776

GHSA-xrjj-mj9h-534m

BIT-golang-2022-41717

GO-2022-1144

cve-program · CVE-2022-41717

euvd · EUVD-2022-7776

nvd · CVE-2022-41717

osv · GHSA-xrjj-mj9h-534m

osv · GO-2022-1144

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current