Bug 2088737 (CVE-2022-29225) - CVE-2022-29225 envoy: Decompressors can be zip bombed
Summary: CVE-2022-29225 envoy: Decompressors can be zip bombed
Alias: CVE-2022-29225
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 2088743
TreeView+ depends on / blocked
Reported: 2022-05-20 11:38 UTC by Avinash Hanwate
Modified: 2022-06-13 16:32 UTC (History)
4 users (show)

Fixed In Version: Envoy 1.22.1, Envoy 1.21.3, Envoy 1.20.4, Envoy 1.19.5
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in Envoy. A specifically constructed HTTP body delivered by an untrusted downstream or upstream peer whose decompressed size is dramatically larger than the compressed size can be sent by an attacker to cause a denial of service.
Clone Of:
Last Closed: 2022-06-13 16:32:22 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5003 0 None None None 2022-06-13 11:55:05 UTC
Red Hat Product Errata RHSA-2022:5004 0 None None None 2022-06-13 12:33:35 UTC

Description Avinash Hanwate 2022-05-20 11:38:14 UTC
Decompressors 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.

Comment 2 errata-xmlrpc 2022-06-13 11:55:03 UTC
This issue has been addressed in the following products:

  OpenShift Service Mesh 2.0

Via RHSA-2022:5003 https://access.redhat.com/errata/RHSA-2022:5003

Comment 3 errata-xmlrpc 2022-06-13 12:33:33 UTC
This issue has been addressed in the following products:

  OpenShift Service Mesh 2.1

Via RHSA-2022:5004 https://access.redhat.com/errata/RHSA-2022:5004

Comment 4 Product Security DevOps Team 2022-06-13 16:32:20 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.