Oracle Retail Clearance Optimization Engine 14.0.5 Dataset memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Oracle Retail Clearance Optimization Engine 14.0.5 and classified as critical. This impacts an unknown function of the component Dataset Component. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2016-1181. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Oracle Retail Clearance Optimization Engine 14.0.5. It has been rated as critical. This issue affects an unknown part of the component Dataset Component. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The weakness was shared 01/15/2020 as Oracle Critical Patch Update Advisory - January 2020 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2016-1181. The exploitation is known to be difficult. 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.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 87288 (Oracle WebLogic Server Multiple Vulnerabilities (CPUAPR2017)).
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 91068†). The entries VDB-88601, VDB-89895, VDB-90013 and VDB-92931 are related to this item. 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: 8.1VulDB Meta Temp Score: 8.0
VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 8.1
Vendor Vector (Oracle): 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: github.com
Timeline
12/26/2015 🔍01/15/2020 🔍
01/15/2020 🔍
01/16/2020 🔍
10/16/2024 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2020
Status: Confirmed
CVE: CVE-2016-1181 (🔍)
GCVE (CVE): GCVE-0-2016-1181
GCVE (VulDB): GCVE-100-148949
SecurityFocus: 91068
SecurityTracker: 1036056
See also: 🔍
Entry
Created: 01/16/2020 08:10Updated: 10/16/2024 08:25
Changes: 01/16/2020 08:10 (52), 01/16/2020 09:02 (16), 03/23/2024 16:52 (21), 10/16/2024 08:25 (2)
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.