CVE-2023-34034GHSA-3H6F-G5F3-GC4W
Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Sp
- 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.6.12, 5.7.10, 5.8.5, 6.0.5, 6.1.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Spring WebFlux, and the potential for a security bypass.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- n/a Spring Security
From Spring Security 6.1.0 · through 6.1.1; From Spring Security 6.0.0 · through 6.0.4; From Spring Security 5.8.0 · through 5.8.4; From Spring Security 5.7.0 · through 5.7.9; From Spring Security 5.6.0 · through 5.6.11
- org.springframework.security:spring-security-configMaven
From 5.6.0 · fixed in 5.6.12
- org.springframework.security:spring-security-configMaven
From 5.7.0 · fixed in 5.7.10
- org.springframework.security:spring-security-configMaven
From 5.8.0 · fixed in 5.8.5
- org.springframework.security:spring-security-configMaven
From 6.0.0 · fixed in 6.0.5
- org.springframework.security:spring-security-configMaven
From 6.1.0 · fixed in 6.1.2