Proxy crash via premature Wasm callbacks
Published Jun 2, 2020 · Updated Aug 4, 2024
Null pointer dereference in Istio Envoy 1.4.0 through 1.4.8 and 1.5.0 through 1.5.3 allows remote attackers to crash proxies. Telemetry v2's Wasm Context invokes data, close, or lifecycle callbacks before the VM context has been created when crafted traffic reaches an ingress gateway or sidecar. Telemetry v2 must be enabled; it is not enabled by default in the 1.4.x branch, and exploitation interrupts the affected proxy's service.
Summary
What happened
Null pointer dereference in Istio Envoy 1.4.0 through 1.4.8 and 1.5.0 through 1.5.3 allows remote attackers to crash proxies. Telemetry v2's Wasm Context invokes data, close, or lifecycle callbacks before the VM context has been created when crafted traffic reaches an ingress gateway or sidecar. Telemetry v2 must be enabled; it is not enabled by default in the 1.4.x branch, and exploitation interrupts the affected proxy's service.
The record
- CVE
- CVE-2020-10739
- Published
- Jun 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Istio
- Product
- Istio Envoy
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.4.0, < 1.4.9
- Affected versionversion=>= 1.5.0, < 1.5.4
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