Authorization bypass via unprefixed double wildcard
Published Mar 27, 2023 · Updated Feb 19, 2025
Authorization bypass in Spring Framework 5.3.0 through 5.3.25 and 6.0.0 through 6.0.6 allows remote attackers to reach protected MVC routes. HandlerMappingIntrospector passes an unprefixed two-asterisk pattern without adding Spring MVC's leading slash, causing the security matcher and route handler to resolve the same request differently. Exposure requires mvcRequestMatcher with that pattern, and successful requests can read or modify resources handled by the incorrectly authorized route.
Summary
What happened
Authorization bypass in Spring Framework 5.3.0 through 5.3.25 and 6.0.0 through 6.0.6 allows remote attackers to reach protected MVC routes. HandlerMappingIntrospector passes an unprefixed two-asterisk pattern without adding Spring MVC's leading slash, causing the security matcher and route handler to resolve the same request differently. Exposure requires mvcRequestMatcher with that pattern, and successful requests can read or modify resources handled by the incorrectly authorized route.
The record
- CVE
- CVE-2023-20860
- Published
- Mar 27, 2023
- Updated
- Feb 19, 2025
- Vendor
- Spring
- Product
- Spring Framework
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record 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=Spring Framework (versions 6.0.0 to 6.0.6 and 5.3.0 to 5.3.25)
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.
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