VDB-101781 · CVE-2016-5007 · BID 91687

Spring Framework 3.1.x/3.2.x/4.0.x/4.2.x URL Pattern Mapping access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Spring Framework 3.1.x/3.2.x/4.0.x/4.2.x. This impacts an unknown function of the component URL Pattern Mapping. Performing a manipulation results in access control. This vulnerability is identified as CVE-2016-5007. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Spring Framework 3.1.x/3.2.x/4.0.x/4.2.x. This affects an unknown functionality of the component URL Pattern Mapping. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 07/07/2016. The weakness was released 05/25/2017 (Website). The advisory is shared at pivotal.io. This vulnerability is uniquely identified as CVE-2016-5007 since 05/24/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 322 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 91687†). Entries connected to this vulnerability are available at VDB-92314, VDB-92773, VDB-92782 and VDB-92786. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.4

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/24/2016 🔍
07/07/2016 +44 days 🔍
07/07/2016 +0 days 🔍
05/25/2017 +322 days 🔍
05/25/2017 +0 days 🔍
05/26/2017 +1 days 🔍
12/25/2020 +1309 days 🔍

Sourcesinfo

Advisory: pivotal.io
Researcher: Clément Notin from INTRINSEC
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-5007 (🔍)
GCVE (CVE): GCVE-0-2016-5007
GCVE (VulDB): GCVE-100-101781
SecurityFocus: 91687 - Spring Security and Spring Framework CVE-2016-5007 Security Bypass Vulnerability
OSVDB: - CVE-2016-5007 - Pivotal Software - Spring Framework - Medium

See also: 🔍

Entryinfo

Created: 05/26/2017 02:58
Updated: 12/25/2020 16:20
Changes: 05/26/2017 02:58 (58), 10/03/2020 09:25 (5), 12/25/2020 16:20 (2)
Complete: 🔍
Cache ID: 216:0D4:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!