VMware SpringSource Spring Security up to 2.0.4 path access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in VMware SpringSource Spring Security up to 2.0.4 and classified as critical. This issue affects some unknown processing. The manipulation of the argument path results in access control. This vulnerability is known as CVE-2010-3700. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in VMware SpringSource Spring Security up to 2.0.4. Affected is an unknown code. The manipulation of the argument path 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 integrity. CVE summarizes:
VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter.
The weakness was published 10/28/2010 as Bug 25015 as not defined bug report (Bugzilla). The advisory is available at issues.apache.org. This vulnerability is traded as CVE-2010-3700 since 10/01/2010. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The exploit is shared for download at packetstormsecurity.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $25k-$100k.
A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 44496†), OSVDB (68931†) and Secunia (SA42024†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
10/01/2010 🔍10/27/2010 🔍
10/28/2010 🔍
10/28/2010 🔍
10/28/2010 🔍
10/29/2010 🔍
03/19/2015 🔍
06/15/2024 🔍
Sources
Vendor: vmware.comAdvisory: Bug 25015
Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-3700 (🔍)
GCVE (CVE): GCVE-0-2010-3700
GCVE (VulDB): GCVE-100-55290
SecurityFocus: 44496 - Spring Security URI Path Parameter Security Bypass Vulnerability
Secunia: 42024
OSVDB: 68931 - Spring Security URL Path Parameter Constraints Bypass
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 03/19/2015 14:37Updated: 06/15/2024 17:47
Changes: 03/19/2015 14:37 (53), 01/04/2018 08:41 (5), 06/15/2024 17:47 (24)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.