Oracle FLEXCUBE Enterprise Limits/Collateral Management 12.0.0/12.1.0 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Oracle FLEXCUBE Enterprise Limits and Collateral Management 12.0.0/12.1.0. Affected is an unknown function of the component Limits/Collateral. The manipulation leads to access control. This vulnerability is documented as CVE-2016-5569. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Oracle FLEXCUBE Enterprise Limits and Collateral Management 12.0.0/12.1.0 (Banking Software). It has been rated as critical. This issue affects some unknown processing of the component Limits/Collateral. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, and integrity.
The weakness was released 10/19/2016 with Oracle as Oracle Critical Patch Update Advisory - October 2016 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2016-5569 since 06/16/2016. The exploitation is known to be easy. The attack may be initiated remotely. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
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 93681†). Entries connected to this vulnerability are available at VDB-4597, VDB-4598, VDB-79101 and VDB-80318. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: Access controlCWE: CWE-284 / CWE-266
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
06/16/2016 🔍10/18/2016 🔍
10/19/2016 🔍
10/19/2016 🔍
10/19/2016 🔍
10/25/2016 🔍
09/27/2022 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - October 2016
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-5569 (🔍)
GCVE (CVE): GCVE-0-2016-5569
GCVE (VulDB): GCVE-100-92861
SecurityFocus: 93681 - Oracle Financial Services Applications CVE-2016-5569 Remote Security Vulnerability
SecurityTracker: 1037049
See also: 🔍
Entry
Created: 10/19/2016 10:22Updated: 09/27/2022 09:38
Changes: 10/19/2016 10:22 (55), 05/13/2019 18:42 (12), 09/27/2022 09:38 (5)
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.