Authorization Bypass of Static Resources in WebFlux Applications
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.7.13, 5.8.15, 6.0.13, 6.1.11, 6.2.7, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 2 proofs of concept on GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under certain circumstances. For this to impact an application, all of the following must be true: • It must be a WebFlux application • It must be using Spring's static resources support • It must have a non-permitAll authorization rule applied to the static resources support
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Spring Security
From 5.7.x · fixed in 5.7.13; From 5.8.x · fixed in 5.8.15; From 6.0.x · fixed in 6.0.13; From 6.1.x · fixed in 6.1.11; From 6.2.x · fixed in 6.2.7; From 6.3.x · fixed in 6.3.4
- org.springframework.security:spring-security-webMaven
From 5.0.0 · fixed in 5.7.13
- org.springframework.security:spring-security-webMaven
From 5.8.0 · fixed in 5.8.15
- org.springframework.security:spring-security-webMaven
From 6.2.0 · fixed in 6.2.7
- org.springframework.security:spring-security-webMaven
From 6.0.0 · fixed in 6.0.13
- org.springframework.security:spring-security-webMaven
From 6.1.0 · fixed in 6.1.11
- org.springframework.security:spring-security-webMaven
From 6.3.0 · fixed in 6.3.4