# CVE-2022-34296: Query predicate bypass in Zalando Skipper

> Attackers can bypass query predicates in Skipper HTTP proxy using prepared requests, undermining 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:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qx2j-85q5-ffp8, GO-2022-0494

## What is CVE-2022-34296?

CVE-2022-34296 is a high-severity vulnerability in n/a, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.

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

3 open source packages ship an affected version, including github.com/zalando/skipper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zalando/skipper` | Go | All versions | 0.13.218 |
| `github.com/zalando/skipper` | Go | All versions | 0.13.218 |
| `github.com/zalando/skipper` | Go | All versions | 0.13.218 |

Products: Zalando Skipper.

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

Upgrade github.com/zalando/skipper to 0.13.218 or later.

## Is CVE-2022-34296 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38580](https://insights.sbomify.com/CVE-2022-38580/): Skipper vulnerable to SSRF via X-Skipper-Proxy (critical 9.8)
- [CVE-2026-23742](https://insights.sbomify.com/CVE-2026-23742/): Skipper arbitrary code execution through lua filters (high 8.8)
- [CVE-2026-24470](https://insights.sbomify.com/CVE-2026-24470/): Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34296 is a high-severity vulnerability in n/a, published on 22 Jun 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-34296 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.13.218
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.13.218
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.13.218

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-34296/ (Markdown: https://insights.sbomify.com/CVE-2022-34296/index.md)
```

## Sources

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

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