Vulnerability Details : 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).
Products affected by CVE-2020-35470
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2020-35470
0.11%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 44 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2020-35470
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
5.8
|
MEDIUM | AV:A/AC:L/Au:N/C:P/I:P/A:P |
6.5
|
6.4
|
NIST | |
|
8.8
|
HIGH | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
2.8
|
5.9
|
NIST |
References for CVE-2020-35470
-
https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1
Comparing v1.16.0...v1.16.1 · envoyproxy/envoy · GitHubPatch;Third Party Advisory
-
https://github.com/envoyproxy/envoy/issues/14087
Wrong %DOWNSTREAM_REMOTE_ADDRESS% logged when using proxy-protocol with tcp-proxy · Issue #14087 · envoyproxy/envoy · GitHubPatch;Third Party Advisory
-
https://github.com/envoyproxy/envoy/pull/14131
proxy protocol: set downstreamRemoteAddress on StreamInfo by ggreenway · Pull Request #14131 · envoyproxy/envoy · GitHubPatch;Third Party Advisory
Jump to