VDB
Sign up
HIGH7.5

GHSA-8crv-49fr-2h6j

Spring Security and Spring Framework may not recognize certain paths that should be protected

Quick fix

GHSA-8crv-49fr-2h6j — org.springframework:spring-core: upgrade to the fixed version with the command below.

# pom.xml: bump <version>4.3.1</version> for org.springframework:spring-core

Details

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x (as well as other unsupported versions) rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

Are you affected?

Enter the version of the package you're using.

Affected packages

Maven/org.springframework:spring-core
Introduced in: 0Fixed in: 4.3.1
Fix# pom.xml: bump <version>4.3.1</version> for org.springframework:spring-core
Maven/org.springframework.security:spring-security-core
Introduced in: 0Fixed in: 4.1.1
Fix# pom.xml: bump <version>4.1.1</version> for org.springframework.security:spring-security-core

References