Categories
CVE-2022-41721

Vulnerability in golang.org/x/net (CVE-2022-41721)

Summary

Vulnerability in golang.org/x/net (CVE-2022-41721). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.1.1-0.20221104162952-702349b0e862 or later.

Original description

The description as published by the source.

A request smuggling attack is possible when using MaxBytesHandler.

When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-41721 has been found in golang.org/x/net.
Risk of unauthorized operations or information disclosure.
What to do: upgrade golang.org/x/net to 0.1.1-0.20221104162952-702349b0e862 or later.
If unsure, ask your IT team or search "golang.org/x/net CVE-2022-41721" on the vendor's site.

CVE-2022-41721 (golang.org/x/net) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.1.1-0.20221104162952-702349b0e862 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-444) exists in golang.org/x/net.

📍 Affected scope

Check the vendor advisory for the affected versions of golang.org/x/net.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.1.1-0.20221104162952-702349b0e862.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang.org/x/net' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'golang.org/x/net' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で golang.org/x/net を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade golang.org/x/net to 0.1.1-0.20221104162952-702349b0e862

    ステージング環境で 0.1.1-0.20221104162952-702349b0e862 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go golang.org/x/net
[{"type":"SEMVER","events":[{"introduced":"0.0.0-20220524220425-1d687d428aca"},{"fixed":"0.1.1-0.20221104162952-702349b0e862"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details