Incorrect concatenation of multiple value request headers in ext-authz extension
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| envoyproxy | envoy | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenShift Service Mesh 1.1 | |||
| servicemesh-proxy-0:1.1.17-2.el8 | cpe:/a:redhat:service_mesh:1.1::el8 | RHSA-2021:3273 | 2021-08-25T00:00:00Z |
| OpenShift Service Mesh 2.0 | |||
| servicemesh-proxy-0:2.0.7-3.el8 | cpe:/a:redhat:service_mesh:2.0::el8 | RHSA-2021:3272 | 2021-08-25T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-19541 | Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions when ext-authz extension is sending request headers to the external authorization service it must merge multiple value headers according to the HTTP spec. However, only the last header value is sent. This may allow specifically crafted requests to bypass authorization. Attackers may be able to escalate privileges when using ext-authz extension or back end service that uses multiple value headers for authorization. A specifically constructed request may be delivered by an untrusted downstream peer in the presence of ext-authz extension. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to the ext-authz extension to correctly merge multiple request header values, when sending request for authorization. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.3% (3.325% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.