Vulnerability in stdlib (CVE-2022-2880)

Summary

Vulnerability in stdlib (CVE-2022-2880). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.18.7, 1.19.2 or later.

Original description

The description as published by the source.

Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

Source: OSV.dev (Open Source Vulnerabilities) NVD 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-2880 has been found in stdlib.
Risk of unauthorized operations or information disclosure.
What to do: upgrade stdlib to 1.18.7, 1.19.2 or later.
If unsure, ask your IT team or search "stdlib CVE-2022-2880" on the vendor's site.

CVE-2022-2880 (stdlib)
Patched: 1.18.7, 1.19.2 — 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 (unclassified) exists in stdlib.

📍 Affected scope

Check the vendor advisory for the affected versions of stdlib.

🔥 Severity

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

🔧 How to fix

Update to 1.18.7, 1.19.2.

🛡️ 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 'stdlib' . 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
Identify exposure identify
```
grep -r 'stdlib' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で stdlib を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade stdlib to 1.18.7, 1.19.2
```
ステージング環境で 1.18.7, 1.19.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go stdlib

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.18.7"},{"introduced":"1.19.0-0"},{"fixed":"1.19.2"}]}]

Bitnami golang

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.18.7"},{"introduced":"1.19.0"},{"fixed":"1.19.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2022-2880 golang-1.15
Ubuntu UBUNTU-CVE-2022-2880 golang-1.10