| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Oracle OpenSSO 7.1/8.0. Affected by this issue is some unknown functionality of the component Administration. The manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2012-0079. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Oracle OpenSSO 7.1/8.0. It has been rated as problematic. This issue affects an unknown functionality of the component Administration. Impacted is integrity. The summary by CVE is:
Unspecified vulnerability in Oracle OpenSSO 7.1 and 8.0 allows remote attackers to affect integrity via unknown vectors related to Administration.
The weakness was disclosed 01/17/2012 with Oracle (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2012-0079 since 12/12/2011. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at oracle.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (72501), SecurityFocus (BID 51492†), OSVDB (78412†), Secunia (SA46646†) and SecurityTracker (ID 1026536†). The entries VDB-4564, VDB-4560, VDB-4566 and VDB-4559 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
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: UnknownCWE: Unknown
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: oracle.com
Timeline
12/12/2011 🔍01/17/2012 🔍
01/17/2012 🔍
01/17/2012 🔍
01/18/2012 🔍
01/18/2012 🔍
01/18/2012 🔍
01/18/2012 🔍
01/22/2012 🔍
04/19/2012 🔍
04/19/2017 🔍
Sources
Vendor: oracle.comAdvisory: oracle.com
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2012-0079 (🔍)
GCVE (CVE): GCVE-0-2012-0079
GCVE (VulDB): GCVE-100-5237
X-Force: 72501 - Oracle Sun OpenSSO component unspecified, Medium Risk
SecurityFocus: 51492 - Oracle OpenSSO CVE-2012-0079 Remote Security Vulnerability
Secunia: 46646 - Oracle OpenSSO Administration Component Data Manipulation Vulnerability, Moderately Critical
OSVDB: 78412
SecurityTracker: 1026536 - Oracle OpenSSO Flaw Lets Remote Users Partially Modify Data
Vulnerability Center: 34288 - [cpujan2012-366304] Oracle OpenSSO 7.1 and 8.0 Unspecified Remote Vulnerability Related to Administrator, Medium
See also: 🔍
Entry
Created: 04/19/2012 21:00Updated: 04/19/2017 10:29
Changes: 04/19/2012 21:00 (65), 04/19/2017 10:29 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.