Skip to content
Fencer Intel
high 8.8

CVE-2020-35470 json

Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the information in the…

published 5y ago modified 2mo ago also BIT-envoy-2020-35470 , EUVD-2020-23142

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

Summary

Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the information in the proxy protocol header. This affects situations with tcp-proxy as the network filter (not HTTP filters).

Patch / fix

  • bitnami envoy 1.16.1
  • envoyproxy envoy 1.16.1

Is CVE-2020-35470 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-35470 updated cvss 8.8

envoy: logs incorrect downstream address making it possible to bypass the RBAC policy

  • Red Hat OpenShift Service Mesh 1 servicemesh-proxy Red Hat OpenShift Service Mesh 2.0 servicemesh-proxy
    not affected: vulnerable code not present

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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami envoy
<1.16.1
1.16.1

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.