CVE-2016-5007
published 2017-05-25CVE-2016-5007: 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…
PriorityP339high7.5CVSS 3.0
AVNACLPRNUINSUCNIHAN
EPSS
2.84%
85.1th percentile
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.
Affected
75 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | libspring-java | < libspring-java 4.3.2-1 (bookworm) | libspring-java 4.3.2-1 (bookworm) |
| pivotal | spring_framework | — | — |
| pivotal | spring_framework | — | — |
| pivotal | spring_framework | — | — |
| pivotal | spring_framework | — | — |
| pivotal | spring_framework | — | — |
| pivotal | spring_security | — | — |
| pivotal | spring_security | — | — |
| pivotal | spring_security | — | — |
| pivotal_software | spring_framework | — | — |
| pivotal_software | spring_framework | — | — |
| pivotal_software | spring_framework | — | — |
| pivotal_software | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
| vmware | spring_framework | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
spring: Path matching inconsistency
vendor_redhat·2016-07-07·CVSS 7.5
CVE-2016-5007 [HIGH] CWE-41 spring: Path matching inconsistency
spring: Path matching inconsistency
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.
It was found that
Debian
CVE-2016-5007: libspring-java - Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, ...
vendor_debian·2016·CVSS 7.5
CVE-2016-5007 [HIGH] CVE-2016-5007: libspring-java - Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, ...
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.
Scope: local
bookworm: resolved (fixed in 4.3.2-1)
bulls
GHSA
Spring Security and Spring Framework may not recognize certain paths that should be protected
ghsa·2018-10-17
CVE-2016-5007 [HIGH] Spring Security and Spring Framework may not recognize certain paths that should be protected
Spring Security and Spring Framework may not recognize certain paths that should be protected
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
OSV
Spring Security and Spring Framework may not recognize certain paths that should be protected
osv·2018-10-17
CVE-2016-5007 [HIGH] Spring Security and Spring Framework may not recognize certain paths that should be protected
Spring Security and Spring Framework may not recognize certain paths that should be protected
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
OSV
CVE-2016-5007: Both Spring Security 3
osv·2017-05-25·CVSS 7.5
CVE-2016-5007 [HIGH] CVE-2016-5007: Both Spring Security 3
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-5007 springframework: spring: Path matching inconsistency [fedora-all]
bugzilla·2016-07-08·CVSS 8.8
CVE-2016-5007 [HIGH] CVE-2016-5007 springframework: spring: Path matching inconsistency [fedora-all]
CVE-2016-5007 springframework: spring: Path matching inconsistency [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions o
Bugzilla
CVE-2016-5007 springframework-security: spring: Path matching inconsistency [fedora-all]
bugzilla·2016-07-08·CVSS 8.8
CVE-2016-5007 [HIGH] CVE-2016-5007 springframework-security: spring: Path matching inconsistency [fedora-all]
CVE-2016-5007 springframework-security: spring: Path matching inconsistency [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported v
Bugzilla
CVE-2016-5007 spring: Path matching inconsistency
bugzilla·2016-07-08·CVSS 8.8
CVE-2016-5007 [HIGH] CVE-2016-5007 spring: Path matching inconsistency
CVE-2016-5007 spring: Path matching inconsistency
Both Spring Security and the Spring Framework rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. It was found that 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.
Affected versions:
Spring Security 3.2.x, 4.0.x, 4.1.0
Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x
Other unsupported versions are also affected
Upstream patches:
https://github.com/spring-projects/spring-framework/commit/a30ab3
https://github.com/spring-projects/spring-security/commit/e4c13e
Upstream b
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.htmlhttp://www.securityfocus.com/bid/91687https://pivotal.io/security/cve-2016-5007https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.htmlhttp://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.htmlhttp://www.securityfocus.com/bid/91687https://pivotal.io/security/cve-2016-5007https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
2017-05-25
Published