Authentication bypass via inconsistent request-path decoding
Published Jun 22, 2020 · Updated Aug 4, 2024
Authentication bypass in Apache Shiro before 1.5.3 allows remote attackers to access protected Spring dynamic-controller routes. WebUtils derives the application path from a request URI and decoded context path, allowing encoded path differences to evade the intended Shiro filter-chain match. Exposure requires a Shiro application using Spring dynamic controllers, and successful requests reach routes without the intended authentication check.
Summary
What happened
Authentication bypass in Apache Shiro before 1.5.3 allows remote attackers to access protected Spring dynamic-controller routes. WebUtils derives the application path from a request URI and decoded context path, allowing encoded path differences to evade the intended Shiro filter-chain match. Exposure requires a Shiro application using Spring dynamic controllers, and successful requests reach routes without the intended authentication check.
The record
- CVE
- CVE-2020-11989
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Shiro
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=Apache Shiro 1.5.2 - 1.5.3
What conditions does exploitation require?
What is affected?
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.
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