Service crash via null route-entry dereference
Published Feb 22, 2022 · Updated Apr 23, 2025
Incorrect control flow in affected Envoy releases allows remote attackers to crash the proxy through a crafted internal redirect. In Filter::convertRequestHeadersForInternalRedirect, the router dereferences routeEntry even when the selected target only has a directResponseEntry. The crash requires internal redirects to select a same-listener direct-response or redirect-action route, terminating the Envoy process.
Summary
What happened
Incorrect control flow in affected Envoy releases allows remote attackers to crash the proxy through a crafted internal redirect. In Filter::convertRequestHeadersForInternalRedirect, the router dereferences routeEntry even when the selected target only has a directResponseEntry. The crash requires internal redirects to select a same-listener direct-response or redirect-action route, terminating the Envoy process.
The record
- CVE
- CVE-2022-21655
- Published
- Feb 22, 2022
- Updated
- Apr 23, 2025
- Vendor
- Envoy Proxy
- Product
- Envoy
- Classifications
- CWE-670, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.18.6
- Affected versionversion=>= 1.19.0, < 1.19.3
- Affected versionversion=>= 1.20.0, < 1.20.2
- Affected versionversion=>= 1.21.0, < 1.21.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo