CVE-2022-41721: GO-2023-1495 - Request smuggling due to improper request handling in golang.org/x/net/http2/h2c

CVE-2022-41721 · Severity: low · CVSS 3.1 · Published 2023-01-13

Request smuggling due to improper request handling in golang.org/x/net/http2/h2c

Technologies: golang.org/x/net (Go). Vendors: Go.

Quick answers

Is CVE-2022-41721 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-41721 being exploited in the wild.
How severe is CVE-2022-41721?
Low severity, with a CVSS score of 3.1, published 13 January 2023.
Which products and versions are affected?
golang.org/x/net (Go) SEMVER:introduced=0.0.0-20220524220425-1d687d428aca,fixed=0.1.1-0.20221104162952-702349b0e862.
Is there a fix for CVE-2022-41721?
Yes. golang.org/x/net (Go): upgrade to 0.1.1-0.20221104162952-702349b0e862 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-41721?
Check whether you run golang.org/x/net (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.1.1-0.20221104162952-702349b0e862 or later
    go get golang.org/x/net@v0.1.1-0.20221104162952-702349b0e862

Affected products

  • golang.org/x/net (Go) SEMVER:introduced=0.0.0-20220524220425-1d687d428aca,fixed=0.1.1-0.20221104162952-702349b0e862

Identifiers

  • CVE-2022-41721
  • GHSA-fxg5-wq6x-vr4w
  • GO-2023-1495

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.