Envoy 1.9.0 and before does not normalize HTTP URL paths. A remote attacker may craft a relative path, e.g., something/../admin, to bypass access control, e.g., a block on /admin. A backend server could then interpret the non-normalized path and provide an attacker access beyond the scope provided for by the access control policy.
References
Link | Resource |
---|---|
https://github.com/envoyproxy/envoy/issues/6435 | Mitigation Issue Tracking Third Party Advisory |
https://github.com/envoyproxy/envoy/security/advisories/GHSA-xcx5-93pw-jw2w | |
https://groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM | |
https://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history | Release Notes Vendor Advisory |
Configurations
History
No history.
Information
Published : 2019-04-25 16:29
Updated : 2023-11-07 03:13
NVD link : CVE-2019-9901
Mitre link : CVE-2019-9901
CVE.ORG link : CVE-2019-9901
JSON object : View
Products Affected
envoyproxy
- envoy
CWE
CWE-706
Use of Incorrectly-Resolved Name or Reference