CVE-2022-34296 json
Query predicate bypass in Zalando Skipper
published 4y ago modified 4mo ago also GHSA-qx2j-85q5-ffp8 , GO-2022-0494 , EUVD-2022-6139
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.
Patch / fix
- go github.com/zalando/skipper 0.13.218
- zalando skipper 0.13.218
- github.com/zalando/skipper@998a658 commit
- github.com/zalando/skipper#2028 pull request
- github.com/zalando/skipper/releases/tag/v0.13.218 release
Is CVE-2022-34296 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/zalando/skipper/releases/tag/v0.13.218 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zalando/skipper | <0.13.218 |
0.13.218 |
References
-
github.com
/zalando/skipper/releases/tag/v0.13.218
web, exploit, patch, release-notes, third-party-advisory
-
github.com
/zalando/skipper/pull/2028
web, patch
-
github.com
/zalando/skipper/commit/998a658ce5a68a336a98f4e63e4371e200860dfc
web, patch
-
nvd.nist.gov
/vuln/detail/CVE-2022-34296
advisory
-
github.com
/zalando/skipper
package
-
github.com
/advisories/GHSA-qx2j-85q5-ffp8
advisory
Sources
- CVE List CVE-2022-34296
- GitHub Advisory GHSA-qx2j-85q5-ffp8
- NVD CVE-2022-34296
- OSV GO-2022-0494
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.