CVE-2020-8664
published 2020-03-04CVE-2020-8664: 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…
PriorityP429medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
1.30%
70.3th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| envoyproxy | envoy | <= 1.13.0 | — |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
CNCF Envoy up to 1.13.0 Access Control authorization (RHSA-2020:0734)
vuldb·2026-10-02·CVSS 5.3
CVE-2020-8664 [MEDIUM] CNCF Envoy up to 1.13.0 Access Control authorization (RHSA-2020:0734)
A vulnerability classified as critical has been found in CNCF Envoy up to 1.13.0. Affected by this issue is some unknown functionality of the component Access Control. This manipulation causes incorrect authorization.
This vulnerability is tracked as CVE-2020-8664. The attack is possible to be carried out remotely. No exploit exists.
Red Hat
envoy: Incorrect Access Control when using SDS with Combined Validation Context
vendor_redhat·2020-03-03·CVSS 5.3
CVE-2020-8664 [MEDIUM] CWE-284 envoy: Incorrect Access Control when using SDS with Combined Validation Context
envoy: Incorrect Access Control when using SDS with Combined Validation Context
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.
An access control bypass vulnerability was found in envoy. When the same TLS secret is used across multiple resources, the client's data, such as the subject alternative name or hash, is not validated. This flaw could lead to a possible bypass of security restrictions.
No detection rules found.
No public exploits indexed.
https://access.redhat.com/errata/RHSA-2020:0734https://github.com/envoyproxy/envoy/security/advisories/GHSA-3x9m-pgmg-xpx8https://www.envoyproxy.io/docs/envoy/v1.13.1/intro/version_historyhttps://access.redhat.com/errata/RHSA-2020:0734https://github.com/envoyproxy/envoy/security/advisories/GHSA-3x9m-pgmg-xpx8https://www.envoyproxy.io/docs/envoy/v1.13.1/intro/version_history
2020-03-04
Published