Incorrect configuration handling allows TLS session re-use without re-validation in Envoy
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| envoyproxy | envoy | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenShift Service Mesh 2.0 | |||
| servicemesh-proxy-0:2.0.9-3.el8 | cpe:/a:redhat:service_mesh:2.0::el8 | RHSA-2022:1276 | 2022-04-07T00:00:00Z |
| OpenShift Service Mesh 2.1 | |||
| servicemesh-proxy-0:2.1.2-4.el8 | cpe:/a:redhat:service_mesh:2.1::el8 | RHSA-2022:1275 | 2022-04-07T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-26872 | Envoy is an open source edge and service proxy, designed for cloud-native applications. Envoy's tls allows re-use when some cert validation settings have changed from their default configuration. The only workaround for this issue is to ensure that default tls settings are used. Users are advised to upgrade. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.087% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|