First published: Tue Dec 15 2020(Updated: )
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).
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Cloud Pak for Security (CP4S) | <=1.6.0.1 | |
IBM Cloud Pak for Security (CP4S) | <=1.6.0.0 | |
IBM Cloud Pak for Security (CP4S) | <=1.5.0.1 | |
IBM Cloud Pak for Security (CP4S) | <=1.5.0.0 | |
IBM Cloud Pak for Security (CP4S) | <=1.4.0.0 | |
Envoy Proxy | <1.16.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-35470 is a vulnerability in Envoy Proxy that could result in weaker than expected security due to the logging of the incorrect downstream address.
Envoy versions up to 1.16.1 and IBM Cloud Pak for Security (CP4S) versions up to 1.6.0.1 are affected by CVE-2020-35470.
CVE-2020-35470 has a severity rating of 8.8 (high).
CVE-2020-35470 impacts Envoy Proxy by logging an incorrect downstream address when using tcp-proxy as the network filter.
To mitigate the risk of CVE-2020-35470, update Envoy Proxy to version 1.16.1 or later.