Authentication bypass via mismatched request-path interpretation
Published Jan 14, 2023 · Updated Aug 2, 2024
Interpretation conflict in Apache Shiro before 1.11.0 with Spring Boot 2.6 and later allows remote attackers to bypass authentication. Shiro assumes Ant-style URL matching, while Spring Boot 2.6 changes its default request matcher, causing the security and routing layers to interpret a crafted path differently. Exposure requires the Shiro-Spring integration with mismatched strategies; a crafted HTTP request can reach application functionality without required authentication.
Summary
What happened
Interpretation conflict in Apache Shiro before 1.11.0 with Spring Boot 2.6 and later allows remote attackers to bypass authentication. Shiro assumes Ant-style URL matching, while Spring Boot 2.6 changes its default request matcher, causing the security and routing layers to interpret a crafted path differently. Exposure requires the Shiro-Spring integration with mismatched strategies; a crafted HTTP request can reach application functionality without required authentication.
The record
- CVE
- CVE-2023-22602
- Published
- Jan 14, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-436, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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