Unauthorized backend access via undecoded escaped slashes
Published May 28, 2021 · Updated Aug 3, 2024
Authorization bypass in Envoy 1.18.2 and earlier allows remote attackers to reach path-restricted backend resources via escaped slashes. Envoy evaluates RBAC or JWT path rules without decoding %2F and %5C, while a backend that later decodes and normalizes the path can route the request to a protected resource. Exploitation requires path-based RBAC or JWT enforcement and a backend that treats escaped and literal slash characters equivalently.
Summary
What happened
Authorization bypass in Envoy 1.18.2 and earlier allows remote attackers to reach path-restricted backend resources via escaped slashes. Envoy evaluates RBAC or JWT path rules without decoding %2F and %5C, while a backend that later decodes and normalizes the path can route the request to a protected resource. Exploitation requires path-based RBAC or JWT enforcement and a backend that treats escaped and literal slash characters equivalently.
The record
- CVE
- CVE-2021-29492
- Published
- May 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Envoy Proxy
- Product
- Envoy
- Classifications
- CWE-551, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.18.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo