Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2022-41717

MEDIUM

CVE-2022-41717 is a medium-severity (CVSS 5.3) CWE-770 vulnerability in golang.org/x/net/http2. O3 Security confirms whether CVE-2022-41717 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asBIT-golang-2022-41717GHSA-xrjj-mj9h-534mGO-2022-1144
Published
Dec 8, 2022
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
🐹golang.org/x/net/http2🐹golang.org/x/net

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogolang.org/x/net/http2all versions0.4.0
🐹Gogolang.org/x/netall versions0.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net/http2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update golang.org/x/net/http2 to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41717 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-41717 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-41717. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-41717 in your dependencies?

O3 detects CVE-2022-41717 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.