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 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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: dell

Published: 2017-05-25T17:00:00

Updated: 2024-08-06T00:46:40.202Z

Reserved: 2016-05-24T00:00:00

Link: CVE-2016-5007

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2017-05-25T17:29:00.740

Modified: 2024-11-21T02:53:25.970

Link: CVE-2016-5007

cve-icon Redhat

Severity : Moderate

Publid Date: 2016-07-07T00:00:00Z

Links: CVE-2016-5007 - Bugzilla