VMware Spring Security 4.0.4
Approved changes feed: RSS · Atom
cpe:2.3:a:vmware:spring_security:4.0.4:*:*:*:*:*:*:*
part: a version: 4.0.4 update: *
| Vendor | Vmware (7bb62c7c-2241-5a0b-8dbc-5f13251fb24e) |
|---|---|
| Product | Spring Security (38556c98-99b3-5c49-9218-a1b581c98cf7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/spring-projects/spring-security |
purl2cpe | 2026-06-01 10:12:21.433128 |
pkg:maven/org.springframework.security/spring-security-core |
purl2cpe | 2026-06-01 10:12:21.433129 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-5007 |
vulnerable | 2026-06-08 05:07:55.976281 |
Details available
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.
Published: 2017-05-25T17:00:00.000Z
Updated: 2024-08-06T00:46:40.202Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.