# CVE-2022-2880: Incorrect sanitization of forwarded query parameters in net/http/httputil

> Attackers can smuggle query parameters through Go ReverseProxy by exploiting unparsable values, bypassing security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2022
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-11129, AZL-37469, AZL-79010, AZL-98748, BIT-golang-2022-2880, DEBIAN-CVE-2022-2880, GHSA-m3hq-grv6-h853, GO-2022-1038, UBUNTU-CVE-2022-2880

## What is CVE-2022-2880?

CVE-2022-2880 is a high-severity vulnerability in Golang Go, published on 14 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2022-2880?

2 open source packages ship an affected version, including golang and stdlib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.18.7, 1.19.2 |
| `stdlib` | Go | All versions | 1.18.7, 1.19.2 |

Products: Golang Go.

## How do I fix CVE-2022-2880?

Upgrade golang to a fixed version for your release line: 1.18.7 or 1.19.2.

## Is CVE-2022-2880 being exploited?

There is no known exploitation of CVE-2022-2880 in the wild and no public exploit code.

## Other vulnerabilities in Golang Go

- [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild)
- [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8)
- [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8)
- [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8)
- [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2880 and fix it if it is affected.

What it is: CVE-2022-2880 is a high-severity vulnerability in Golang Go, published on 14 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2880 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.18.7, 1.19.2
- stdlib (Go): affected all versions; fixed in 1.18.7, 1.19.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2880/ (Markdown: https://insights.sbomify.com/CVE-2022-2880/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2880
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2880
- OSV: https://osv.dev/vulnerability/CVE-2022-2880

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2880/
Summaries are generated and may contain mistakes; the official description above is the record.