Unauthorized resource access via duplicate controller mappings
Published Oct 28, 2021 · Updated Aug 3, 2024
Authorization bypass in Spring Data REST 3.4.0 through 3.4.13 and 3.5.0 through 3.5.5 allows remote attackers to access HTTP resources. A type-level request mapping on a custom controller is registered both beneath the configured base API path and at the same path without that prefix. Exploitation requires a nonempty base path and security rules that protect only the prefixed URI, exposing the unprefixed controller resource without the intended authorization.
Summary
What happened
Authorization bypass in Spring Data REST 3.4.0 through 3.4.13 and 3.5.0 through 3.5.5 allows remote attackers to access HTTP resources. A type-level request mapping on a custom controller is registered both beneath the configured base API path and at the same path without that prefix. Exploitation requires a nonempty base path and security rules that protect only the prefixed URI, exposing the unprefixed controller resource without the intended authorization.
The record
- CVE
- CVE-2021-22047
- Published
- Oct 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Spring
- Product
- Spring Data REST
- Classifications
- CWE-200, CWE-668, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 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=Spring Data REST versions 3.4.x prior to 3.4.14+ ,3.5.x prior to 3.5.6+ and old unsupported versions
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