VMware SpringSource Spring Security up to 2.0.6 Serialization access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in VMware SpringSource Spring Security up to 2.0.6 and classified as critical. Affected by this issue is some unknown functionality of the component Serialization. The manipulation results in access control. This vulnerability was named CVE-2011-2894. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in VMware SpringSource Spring Security up to 2.0.6. Affected is an unknown code of the component Serialization. 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. CVE summarizes:
Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) serializing a java.lang.Proxy instance and using InvocationHandler, or (2) accessing internal AOP interfaces, as demonstrated using deserialization of a DefaultListableBeanFactory instance to execute arbitrary commands via the java.lang.Runtime class.
The weakness was presented 10/04/2011 (Website). The advisory is available at securityfocus.com. This vulnerability is traded as CVE-2011-2894 since 07/27/2011. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability is also documented in the databases at X-Force (69687), SecurityFocus (BID 49536†), OSVDB (75263†) and Secunia (SA45942†). 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: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
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: 🔍
Status: Unproven
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: 🔍
0-Day Time: 🔍
Timeline
07/27/2011 🔍09/09/2011 🔍
10/04/2011 🔍
10/04/2011 🔍
03/23/2015 🔍
11/23/2021 🔍
Sources
Vendor: vmware.comAdvisory: RHSA-2011:1334⛔
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2011-2894 (🔍)
GCVE (CVE): GCVE-0-2011-2894
GCVE (VulDB): GCVE-100-58818
X-Force: 69687 - Spring Framework and Spring Security object security bypass
SecurityFocus: 49536 - Spring Framework and Spring Security Remote Security Bypass Vulnerability
Secunia: 45942
OSVDB: 75263
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 03/23/2015 16:50Updated: 11/23/2021 08:07
Changes: 03/23/2015 16:50 (50), 01/15/2018 11:49 (6), 11/23/2021 08:07 (3)
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.