CVE-2020-35470

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).

8.8

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.78% Top 30%

Third-Party Advisory github.com Third-Party Advisory github.com Third-Party Advisory github.com

Affected: n/a n/a

References

Link	Tags
https://github.com/envoyproxy/envoy/issues/14087	third party advisory patch
https://github.com/envoyproxy/envoy/pull/14131	third party advisory patch
https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1	third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2020-35470?: CVE-2020-35470 has been scored as a high severity vulnerability.
How to fix CVE-2020-35470?: To fix CVE-2020-35470, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-35470 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-35470 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.