CVE-2022-29225 json
Zip bomb vulnerability in Envoy
published 2022-06-09 4 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2022-29225 , EUVD-2022-33587 , GHSA-75hv-2jjj-89hh
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Envoy is a cloud-native high-performance proxy. In versions prior to 1.22.1 secompressors accumulate decompressed data into an intermediate buffer before overwriting the body in the decode/encodeBody. This may allow an attacker to zip bomb the decompressor by sending a small highly compressed payload. Maliciously constructed zip files may exhaust system memory and cause a denial of service. Users are advised to upgrade. Users unable to upgrade may consider disabling decompression.
Patch / fix
- bitnami envoy 1.22.1
- envoyproxy envoy 1.22.1
- servicemesh service mesh 2.1 2.1.3-1.el8
- servicemesh-cni service mesh 2.1 2.1.3-1.el8
- servicemesh-proxy service mesh 2.1 2.1.3-1.el8
- servicemesh-operator service mesh 2.1 2.1.3-2.el8
- servicemesh-ratelimit service mesh 2.1 2.1.3-1.el8
- servicemesh-prometheus service mesh 2.1 2.23.0-7.el8
- servicemesh-proxy-wasm service mesh 2.1 2.1.3-1.el8
- servicemesh-pilot-agent service mesh 2.1 2.1.3-1.el8
red hat advisories RHSA-2022:5004RHSA-2022:5003
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-29225 updated cvss 7.5
envoy: Decompressors can be zip bombed
-
Red Hat OpenShift Service Mesh 2.0 servicemesh-proxy 2.0.10-1.el8fixed: vendor fix “This can be mitigated by disabling decompression in Envoy.” RHSA-2022:5003
-
Red Hat OpenShift Service Mesh 2.1 servicemesh-proxy 2.1.3-1.el8, servicemesh-proxy-wasm 2.1.3-1.el8fixed: vendor fix “This can be mitigated by disabling decompression in Envoy.” RHSA-2022:5004
-
Red Hat OpenShift Service Mesh 2.0 servicemesh 2.0.10-1.el8, servicemesh-cni 2.0.10-1.el8, servicemesh-mixc 2.0.10-1.el8, servicemesh-mixs 2.0.10-1.el8, servicemesh-istioctl 2.0.10-1.el8, servicemesh-operator 2.0.10-1.el8, +3 more Red Hat OpenShift Service Mesh 2.1 servicemesh 2.1.3-1.el8, servicemesh-cni 2.1.3-1.el8, servicemesh-operator 2.1.3-2.el8, servicemesh-ratelimit 2.1.3-1.el8, servicemesh-pilot-agent 2.1.3-1.el8, servicemesh-prometheus 2.23.0-7.el8, +1 morenot affected: vulnerable code not present “This can be mitigated by disabling decompression in Envoy.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-75hv-2jjj-89hh referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | envoy | <1.22.1 |
1.22.1 |
Affected products
- envoyproxy envoy
Classification
References
-
github.com
/envoyproxy/envoy/commit/cb4ef0b09200c720dfdb07e097092dd105450343
patch, third-party-advisory, advisory
-
github.com
/envoyproxy/envoy/security/advisories/GHSA-75hv-2jjj-89hh
exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29225
web
Sources
- CVE List CVE-2022-29225
- NVD CVE-2022-29225
- OSV BIT-envoy-2022-29225
Fencer Vulns 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.