Bypass of path matching rules using escaped slash characters
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.14-1.el8 | cpe:/a:redhat:service_mesh:1.1::el8 | RHSA-2021:1540 | 2021-05-11T00:00:00Z |
| OpenShift Service Mesh 2.0 | |||
| servicemesh-operator-0:2.0.4-3.el8 | cpe:/a:redhat:service_mesh:2.0::el8 | RHSA-2021:1538 | 2021-05-11T00:00:00Z |
| servicemesh-proxy-0:2.0.4-1.el8 | cpe:/a:redhat:service_mesh:2.0::el8 | RHSA-2021:1538 | 2021-05-11T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-16089 | Envoy is a cloud-native edge/middle/service proxy. Envoy does not decode escaped slash sequences `%2F` and `%5C` in HTTP URL paths in versions 1.18.2 and before. A remote attacker may craft a path with escaped slashes, e.g. `/something%2F..%2Fadmin`, to bypass access control, e.g. a block on `/admin`. A backend server could then decode slash sequences and normalize path and provide an attacker access beyond the scope provided for by the access control policy. ### Impact Escalation of Privileges when using RBAC or JWT filters with enforcement based on URL path. Users with back end servers that interpret `%2F` and `/` and `%5C` and `\` interchangeably are impacted. ### Attack Vector URL paths containing escaped slash characters delivered by untrusted client. Patches in versions 1.18.3, 1.17.3, 1.16.4, 1.15.5 contain new path normalization option to decode escaped slash characters. As a workaround, if back end servers treat `%2F` and `/` and `%5C` and `\` interchangeably and a URL path based access control is configured, one may reconfigure the back end server to not treat `%2F` and `/` and `%5C` and `\` interchangeably. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 63.1% (63.096% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.