Back to Database
Status published
High
CVE-2020-35470
Envoy before 1.16.1 logs an incorrect downstream address because it...
Vulnerability Description
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).
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-35470
Credits & Attribution
No credits recorded in the NVD database.
References
More from envoyproxy
View All →CVE-2025-66220
Envoy’s TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte
Medium
5
CVE-2025-64763
Envoy forwards early CONNECT data in TCP proxy mode
Low
3.7
CVE-2025-64527
Envoy crashes when JWT authentication is configured with the remote JWKS fetching
Medium
6.5
CVE-2025-62504
Envoy Lua filter use-after-free when oversized rewritten response body causes crash
Medium
6.5
CVE-2025-62409
Envoy allows large requests and responses to cause TCP connection pool crash
Medium
6.6
Affected Vendor
envoyproxy
View all reports →Affected Software
envoy
Vulnerable Versions:
0
Timeline
Official Publish:
December 15th, 2020
Last Modified:
August 4th, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.