envoyproxy/envoy: crash with empty HTTP/2 metadata map
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenShift Service Mesh 1.1 | |||
| servicemesh-proxy-0:1.1.13-1.el8 | cpe:/a:redhat:service_mesh:1.1::el8 | RHSA-2021:1322 | 2021-04-22T00:00:00Z |
| OpenShift Service Mesh 2.0 | |||
| servicemesh-proxy-0:2.0.3-1.el8 | cpe:/a:redhat:service_mesh:2.0::el8 | RHSA-2021:1324 | 2021-04-22T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-15897 | An issue was discovered in Envoy 1.14.0. There is a remotely exploitable crash for HTTP2 Metadata, because an empty METADATA map triggers a Reachable Assertion. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.8% (1.772% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.