Attacker Value
Unknown
(0 users assessed)
Exploitability
Unknown
(0 users assessed)
User Interaction
None
Privileges Required
None
Attack Vector
Network
0

CVE-2016-5007

Disclosure Date: May 25, 2017 •
CVE-2016-5007 CVSS v3 Base Score: 7.5
Add MITRE ATT&CK tactics and techniques that apply to this CVE.

Description

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.

Add Assessment

No one has assessed this topic. Be the first to add your voice to the community.

CVSS V3 Severity and Metrics
Base Score:
7.5 High
Impact Score:
3.6
Exploitability Score:
3.9
Vector:
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack Vector (AV):
Network
Attack Complexity (AC):
Low
Privileges Required (PR):
None
User Interaction (UI):
None
Scope (S):
Unchanged
Confidentiality (C):
None
Integrity (I):
High
Availability (A):
None

General Information

Offensive Application
Unknown
Utility Class
Unknown
Ports
Unknown
OS
Unknown
Vulnerable Versions
Spring Security 3.2.x
Spring Security 4.0.x
Spring Security 4.1.0
Spring Framework 3.2.x
Spring Framework 4.0.x
Spring Framework 4.1.x
Spring Framework 4.2.x
Spring Framework older unsupported versions are also affected
Prerequisites
Unknown
Discovered By
Unknown
PoC Author
Unknown
Metasploit Module
Unknown
Reporter
Unknown

Vendors

  • pivotal software,
  • vmware

Products

  • spring framework 3.2.0,
  • spring framework 3.2.1,
  • spring framework 3.2.10,
  • spring framework 3.2.11,
  • spring framework 3.2.12,
  • spring framework 3.2.13,
  • spring framework 3.2.14,
  • spring framework 3.2.15,
  • spring framework 3.2.16,
  • spring framework 3.2.17,
  • spring framework 3.2.18,
  • spring framework 3.2.2,
  • spring framework 3.2.3,
  • spring framework 3.2.4,
  • spring framework 3.2.5,
  • spring framework 3.2.6,
  • spring framework 3.2.7,
  • spring framework 3.2.8,
  • spring framework 3.2.9,
  • spring framework 4.0.0,
  • spring framework 4.0.1,
  • spring framework 4.0.2,
  • spring framework 4.0.3,
  • spring framework 4.0.4,
  • spring framework 4.0.5,
  • spring framework 4.0.6,
  • spring framework 4.0.7,
  • spring framework 4.0.8,
  • spring framework 4.0.9,
  • spring framework 4.1.0,
  • spring framework 4.1.1,
  • spring framework 4.1.2,
  • spring framework 4.1.3,
  • spring framework 4.1.4,
  • spring framework 4.1.5,
  • spring framework 4.1.6,
  • spring framework 4.1.7,
  • spring framework 4.1.8,
  • spring framework 4.1.9,
  • spring framework 4.2.0,
  • spring framework 4.2.1,
  • spring framework 4.2.2,
  • spring framework 4.2.3,
  • spring framework 4.2.4,
  • spring framework 4.2.5,
  • spring framework 4.2.6,
  • spring framework 4.2.7,
  • spring framework 4.2.8,
  • spring framework 4.2.9,
  • spring security 3.2.0,
  • spring security 3.2.1,
  • spring security 3.2.10,
  • spring security 3.2.2,
  • spring security 3.2.3,
  • spring security 3.2.4,
  • spring security 3.2.5,
  • spring security 3.2.6,
  • spring security 3.2.7,
  • spring security 3.2.8,
  • spring security 3.2.9,
  • spring security 4.0.0,
  • spring security 4.0.1,
  • spring security 4.0.2,
  • spring security 4.0.3,
  • spring security 4.0.4,
  • spring security 4.1.0

Additional Info

Authenticated
Unknown
Exploitable
Unknown
Reliability
Unknown
Stability
Unknown
Available Mitigations
Unknown
Shelf Life
Unknown
Userbase/Installbase
Unknown
Patch Effectiveness
Unknown
Technical Analysis