envoyproxy/envoy: incorrectly handles multiple HTTP headers in requests
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenShift Service Mesh 1.1 | |||
| servicemesh-proxy-0:1.1.9-1.el8 | cpe:/a:redhat:service_mesh:1.1::el8 | RHSA-2020:4129 | 2020-09-30T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-17716 | Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.3% (1.317% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.