CVE-2020-25017
First published: Thu Oct 01 2020(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Envoyproxy Envoy | <1.12.7 | |
| Envoyproxy Envoy | >=1.13.0<1.13.4 | |
| Envoyproxy Envoy | >=1.14.0<1.14.4 | |
| Envoyproxy Envoy | >=1.15.0<1.15.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2020-25017?
CVE-2020-25017 is a vulnerability in Envoy through version 1.15.0 that only considers the first value when multiple header values are present for some HTTP headers.
How does the vulnerability in CVE-2020-25017 affect Envoy?
The vulnerability in CVE-2020-25017 affects Envoy through version 1.15.0 by not replacing all existing occurrences of a non-inline header when using Envoy's setCopy() header map API.
What is the severity of CVE-2020-25017?
The severity of CVE-2020-25017 is rated as high, with a CVSS score of 8.3.
Which software versions are affected by CVE-2020-25017?
Envoy versions 1.12.7, 1.13.0 to 1.13.4, 1.14.0 to 1.14.4, and 1.15.0 to 1.15.1 are affected by CVE-2020-25017.
How can I find more information about CVE-2020-25017?
You can find more information about CVE-2020-25017 on the Envoyproxy GitHub repository and the Envoy Security Announce Google Group.
- collector/nvd-index
- agent/type
- vendor/envoyproxy
- canonical/envoyproxy envoy
- version/envoyproxy envoy/1.13.0
- version/envoyproxy envoy/1.14.0
- version/envoyproxy envoy/1.15.0