Protected-data disclosure via omitted method security advice
Published Aug 20, 2024 · Updated Aug 20, 2024
Missing authorization in Spring Security 6.3.0 and 6.3.1 allows remote attackers to bypass method authorization and read protected data. The proxying path for @AuthorizeReturnObject and AuthorizationAdvisorProxyFactory omits @PreFilter, @PostFilter, @PreAuthorize, or @PostAuthorize advice on wrapped objects. Exposure requires AnnotationAwareAspectJAutoProxyCreator, a FactoryBean, enabled method security, a wrapped object, and one of the affected annotations.
Summary
What happened
Missing authorization in Spring Security 6.3.0 and 6.3.1 allows remote attackers to bypass method authorization and read protected data. The proxying path for @AuthorizeReturnObject and AuthorizationAdvisorProxyFactory omits @PreFilter, @PostFilter, @PreAuthorize, or @PostAuthorize advice on wrapped objects. Exposure requires AnnotationAwareAspectJAutoProxyCreator, a FactoryBean, enabled method security, a wrapped object, and one of the affected annotations.
The record
- CVE
- CVE-2024-38810
- Published
- Aug 20, 2024
- Updated
- Aug 20, 2024
- Vendor
- Spring
- Product
- Spring Security
- Classifications
- CWE-862, CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=6.3.x <6.3.2
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