CVE-2022-41717: GO-2022-1144 - Excessive memory growth in net/http and golang.org/x/net/http2

Quick answers

Is CVE-2022-41717 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-41717 being exploited in the wild.

How severe is CVE-2022-41717?

Low severity, with a CVSS score of 3.1, published 8 December 2022.

Which products and versions are affected?

golang.org/x/net (Go) SEMVER:introduced=0,fixed=0.4.0; golang.org/x/net/http2 (Go) SEMVER:introduced=0,fixed=0.4.0; stdlib (Go) SEMVER:introduced=0,fixed=1.18.9,introduced=1.19.0-0,fixed=1.19.4.

Is there a fix for CVE-2022-41717?

Yes. golang.org/x/net (Go): upgrade to 0.4.0 or later; golang.org/x/net/http2 (Go): upgrade to 0.4.0 or later; stdlib (Go): upgrade to 1.19.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-41717?

Check whether you run golang.org/x/net (Go), golang.org/x/net/http2 (Go) or stdlib (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• golang.org/x/net (Go): upgrade to 0.4.0 or later

  go get golang.org/x/net@v0.4.0

• golang.org/x/net/http2 (Go): upgrade to 0.4.0 or later

  go get golang.org/x/net/http2@v0.4.0

• stdlib (Go): upgrade to 1.19.4 or later

  go get stdlib@v1.19.4

Affected products

• golang.org/x/net (Go) SEMVER:introduced=0,fixed=0.4.0
• golang.org/x/net/http2 (Go) SEMVER:introduced=0,fixed=0.4.0
• stdlib (Go) SEMVER:introduced=0,fixed=1.18.9,introduced=1.19.0-0,fixed=1.19.4

Identifiers

• CVE-2022-41717
• GHSA-xrjj-mj9h-534m
• GO-2022-1144