Security readout for executives and security teams
Plain-English summary
Envoy versions before 1.22.1 can be forced to use excessive memory when handling specially compressed data. A small compressed payload may expand into a large intermediate buffer and crash or degrade the proxy, causing service disruption. The published remedy is to upgrade, or disable decompression if upgrading is not immediately possible.
Executive priority
Treat as a high-priority availability issue for Envoy-backed services. It is not described as data compromise, but affected internet-facing proxies could be disrupted cheaply. Patch or disable decompression where exposed.
Technical view
The flaw is a zip-bomb style denial-of-service in Envoy decompression. Before 1.22.1, decompressors accumulated decompressed content in an intermediate buffer before replacing the body in encodeBody/decodeBody. This can exhaust memory from network-reachable traffic without authentication, matching CVSS 7.5 and CWE-400/CWE-409.
Likely exposure
Exposure is most likely where Envoy before 1.22.1 is deployed as an edge, service-mesh, or internal proxy with decompression enabled and accepts compressed traffic from untrusted clients or upstreams.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability is network reachable, low complexity, unauthenticated, and affects availability only. Evidence supports denial-of-service risk, not data theft or code execution.
Researcher notes
Focus validation on version, decompression configuration, and traffic trust boundaries. The root issue is unbounded resource consumption during decompressed body buffering, categorized as CWE-400 and CWE-409. Do not infer affected downstream products without confirming their bundled Envoy version and configuration.
Mitigation direction
- Upgrade Envoy to version 1.22.1 or later.
- If upgrade is delayed, consider disabling decompression as vendor guidance states.
- Prioritize externally reachable and high-traffic Envoy deployments first.
- Review Envoy security advisory and release guidance before operational changes.
Validation and detection
- Inventory all Envoy deployments and confirm running versions.
- Identify listeners, filters, or routes where decompression is enabled.
- Check whether compressed traffic can arrive from untrusted sources.
- Review memory exhaustion, OOM, crash, and restart telemetry around Envoy.
- Confirm upgraded instances report Envoy 1.22.1 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-409: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-29225 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-75hv-2jjj-89hhCVE reference · x_refsource_CONFIRM
- https://github.com/envoyproxy/envoy/commit/cb4ef0b09200c720dfdb07e097092dd105450343CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Handling of Highly Compressed Data (Data Amplification)
Improper Handling of Highly Compressed Data (Data Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.