{"id":"CVE-2020-35470","aliases":["BIT-envoy-2020-35470"],"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.","published_at":"2020-11-21T00:00:00Z","modified_at":"2026-09-08T08:47:23.779314Z","products":[],"rating":{"severity":"high","score":8.8,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attack_path":"adjacent","user_interaction":false,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.009859999641776085,"percentile":0.6313599944114685,"date":"2026-11-19T00:00:00Z"},"priority":8.8,"details":"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).","affected_stack":[],"affected_other":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.16.1"}]}],"fixed":["1.16.1"],"provider":"osv","source":"BIT-envoy-2020-35470","relation":"self"},{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.1"}]}],"fixed":["1.16.1"],"provider":"nvd","source":"CVE-2020-35470","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"not_affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2020-35470"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.0","cpe":"cpe:/a:redhat:service_mesh:2.0","status":"not_affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2020-35470"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2020-35470","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2020-35470","license":"CC-BY-4.0","published_at":"2020-12-15T00:48:35Z","modified_at":"2024-08-04T17:02:08.057Z","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.","details":"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).","severity":[],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/14087"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/pull/14131"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1"}]},{"provider":"nvd","source_id":"CVE-2020-35470","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35470","severity":[],"affected":[{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.1"}]}],"fixed":["1.16.1"],"provider":"nvd","source":"CVE-2020-35470","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"BIT-envoy-2020-35470","relation":"self","url":"https://osv.dev/vulnerability/BIT-envoy-2020-35470","license":"Apache-2.0","published_at":"2024-03-06T11:00:08.11Z","modified_at":"2026-09-08T08:47:23.779314Z","details":"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).","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","source":"BIT-envoy-2020-35470"}],"affected":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.16.1"}]}],"fixed":["1.16.1"],"provider":"osv","source":"BIT-envoy-2020-35470","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1"},{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/issues/14087"},{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/pull/14131"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35470"}]},{"provider":"redhat-vex","source_id":"CVE-2020-35470","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2020-35470","license":"CC-BY-4.0","published_at":"2020-11-21T00:00:00Z","modified_at":"2023-08-30T23:50:49Z","summary":"envoy: logs incorrect downstream address making it possible to bypass the RBAC policy","details":"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).","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","source":"CVE-2020-35470"},{"type":"Red Hat","score":"Moderate","source":"CVE-2020-35470"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"not_affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2020-35470"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.0","cpe":"cpe:/a:redhat:service_mesh:2.0","status":"not_affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2020-35470"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-35470.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-35470"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1907805"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-35470"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35470"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/14087"}]}],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/14087"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/pull/14131"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35470"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-35470.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-35470"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1907805"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-35470"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2020-35470","url":"https://www.cve.org/CVERecord?id=CVE-2020-35470","license":"CC-BY-4.0","modified_at":"2024-08-04T17:02:08.057Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2020-35470","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35470","relation":"self"},{"provider":"osv","source_id":"BIT-envoy-2020-35470","url":"https://osv.dev/vulnerability/BIT-envoy-2020-35470","license":"Apache-2.0","modified_at":"2026-09-08T08:47:23.779314Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2020-35470","url":"https://access.redhat.com/security/cve/CVE-2020-35470","license":"CC-BY-4.0","modified_at":"2023-08-30T23:50:49Z","relation":"self"}]}
