envoy: Incorrect Access Control when using SDS with Combined Validation Context
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 |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenShift Service Mesh 1.0 | |||
| servicemesh-proxy-0:1.0.9-2.el8 | cpe:/a:redhat:service_mesh:1.0::el8 | RHSA-2020:0734 | 2020-03-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-29512 | CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not applied, even though it was visible in the active config dump. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.3% (1.300% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Envoyproxy
Envoyproxy envoy |
|
| CPEs | cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Cncf
Cncf envoy |
Envoyproxy
Envoyproxy envoy |