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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts integrity (unauthorized modifications), for affected systems. Impacting 3 products from pivotal_software, from vmware, from vmware organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-05-25T17:29:00.740
2025-04-20T01:37:25.860
Deferred
CVSSv3.0: 7.5 (HIGH)
AV:N/AC:L/Au:N/C:N/I:P/A:N
10.0
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | pivotal_software | spring_framework | 3.2.0 | Yes |
| Application | pivotal_software | spring_framework | 4.0.0 | Yes |
| Application | pivotal_software | spring_framework | 4.1.0 | Yes |
| Application | pivotal_software | spring_framework | 4.2.0 | Yes |
| Application | vmware | spring_framework | 3.2.1 | Yes |
| Application | vmware | spring_framework | 3.2.2 | Yes |
| Application | vmware | spring_framework | 3.2.3 | Yes |
| Application | vmware | spring_framework | 3.2.4 | Yes |
| Application | vmware | spring_framework | 3.2.5 | Yes |
| Application | vmware | spring_framework | 3.2.6 | Yes |
| Application | vmware | spring_framework | 3.2.7 | Yes |
| Application | vmware | spring_framework | 3.2.8 | Yes |
| Application | vmware | spring_framework | 3.2.9 | Yes |
| Application | vmware | spring_framework | 3.2.10 | Yes |
| Application | vmware | spring_framework | 3.2.11 | Yes |
| Application | vmware | spring_framework | 3.2.12 | Yes |
| Application | vmware | spring_framework | 3.2.13 | Yes |
| Application | vmware | spring_framework | 3.2.14 | Yes |
| Application | vmware | spring_framework | 3.2.15 | Yes |
| Application | vmware | spring_framework | 3.2.16 | Yes |
| Application | vmware | spring_framework | 3.2.17 | Yes |
| Application | vmware | spring_framework | 3.2.18 | Yes |
| Application | vmware | spring_framework | 4.0.1 | Yes |
| Application | vmware | spring_framework | 4.0.2 | Yes |
| Application | vmware | spring_framework | 4.0.3 | Yes |
| Application | vmware | spring_framework | 4.0.4 | Yes |
| Application | vmware | spring_framework | 4.0.5 | Yes |
| Application | vmware | spring_framework | 4.0.6 | Yes |
| Application | vmware | spring_framework | 4.0.7 | Yes |
| Application | vmware | spring_framework | 4.0.8 | Yes |
| Application | vmware | spring_framework | 4.0.9 | Yes |
| Application | vmware | spring_framework | 4.1.1 | Yes |
| Application | vmware | spring_framework | 4.1.2 | Yes |
| Application | vmware | spring_framework | 4.1.3 | Yes |
| Application | vmware | spring_framework | 4.1.4 | Yes |
| Application | vmware | spring_framework | 4.1.5 | Yes |
| Application | vmware | spring_framework | 4.1.6 | Yes |
| Application | vmware | spring_framework | 4.1.7 | Yes |
| Application | vmware | spring_framework | 4.1.8 | Yes |
| Application | vmware | spring_framework | 4.1.9 | Yes |
| Application | vmware | spring_framework | 4.2.1 | Yes |
| Application | vmware | spring_framework | 4.2.2 | Yes |
| Application | vmware | spring_framework | 4.2.3 | Yes |
| Application | vmware | spring_framework | 4.2.4 | Yes |
| Application | vmware | spring_framework | 4.2.5 | Yes |
| Application | vmware | spring_framework | 4.2.6 | Yes |
| Application | vmware | spring_framework | 4.2.7 | Yes |
| Application | vmware | spring_framework | 4.2.8 | Yes |
| Application | vmware | spring_framework | 4.2.9 | Yes |
| Application | vmware | spring_security | 3.2.0 | Yes |
| Application | vmware | spring_security | 3.2.1 | Yes |
| Application | vmware | spring_security | 3.2.2 | Yes |
| Application | vmware | spring_security | 3.2.3 | Yes |
| Application | vmware | spring_security | 3.2.4 | Yes |
| Application | vmware | spring_security | 3.2.5 | Yes |
| Application | vmware | spring_security | 3.2.6 | Yes |
| Application | vmware | spring_security | 3.2.7 | Yes |
| Application | vmware | spring_security | 3.2.8 | Yes |
| Application | vmware | spring_security | 3.2.9 | Yes |
| Application | vmware | spring_security | 3.2.10 | Yes |
| Application | vmware | spring_security | 4.0.0 | Yes |
| Application | vmware | spring_security | 4.0.1 | Yes |
| Application | vmware | spring_security | 4.0.2 | Yes |
| Application | vmware | spring_security | 4.0.3 | Yes |
| Application | vmware | spring_security | 4.0.4 | Yes |
| Application | vmware | spring_security | 4.1.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For pivotal_software's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.