Skip to content
Fencer Intel
medium 5.3

CVE-2020-8664 json

CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context.

published 6y ago modified last mo. also BIT-envoy-2020-8664 , EUVD-2020-29512 , GHSA-3x9m-pgmg-xpx8

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

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.

Patch / fix

  • servicemesh-proxy service mesh 1.0 1.0.9-2.el8

red hat advisories RHSA-2020:0734

Is CVE-2020-8664 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-8664 updated cvss 7.3

envoy: Incorrect Access Control when using SDS with Combined Validation Context

  • Red Hat OpenShift Service Mesh 1.0 servicemesh-proxy 1.0.9-2.el8
    fixed: vendor fix RHSA-2020:0734

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami envoy
<=1.13.0
no fix listed

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.