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://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history | Release Notes Vendor Advisory |
https://groups.google.com/forum/#!topic/envoy-announce/VoHfnDqZiAM | Patch Third Party Advisory |
https://github.com/envoyproxy/envoy/issues/6435 | Mitigation Issue Tracking Third Party Advisory |
https://github.com/envoyproxy/envoy/security/advisories/GHSA-xcx5-93pw-jw2w |
Configurations
Information
Published : 2019-04-25 09:29
Updated : 2020-08-24 10:37
NVD link : CVE-2019-9901
Mitre link : CVE-2019-9901
JSON object : View
CWE
CWE-706
Use of Incorrectly-Resolved Name or Reference
Products Affected
envoyproxy
- envoy