CVE-2020-35470

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

Configuration 1 (hide)

cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*

History

21 Nov 2024, 05:27

Type Values Removed Values Added
References () https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1 - Patch, Third Party Advisory () https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1 - Patch, Third Party Advisory
References () https://github.com/envoyproxy/envoy/issues/14087 - Patch, Third Party Advisory () https://github.com/envoyproxy/envoy/issues/14087 - Patch, Third Party Advisory
References () https://github.com/envoyproxy/envoy/pull/14131 - Patch, Third Party Advisory () https://github.com/envoyproxy/envoy/pull/14131 - Patch, Third Party Advisory

Information

Published : 2020-12-15 01:15

Updated : 2024-11-21 05:27


NVD link : CVE-2020-35470

Mitre link : CVE-2020-35470

CVE.ORG link : CVE-2020-35470


JSON object : View

Products Affected

envoyproxy

  • envoy