Oracle FLEXCUBE Universal Banking up to 14.1.0 Infrastructure access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Oracle FLEXCUBE Universal Banking up to 14.1.0. This impacts an unknown function of the component Infrastructure. This manipulation causes access control. The identification of this vulnerability is CVE-2018-2981. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Oracle FLEXCUBE Universal Banking up to 14.1.0 (Banking Software). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Infrastructure. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, and integrity.
The bug was discovered 07/17/2018. The weakness was shared 07/18/2018 with Oracle as Oracle Critical Patch Update Advisory - July 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2018-2981 since 12/15/2017. The attack can be launched remotely. A single authentication is required for exploitation. 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 104778†). The entries VDB-79791, VDB-95830, VDB-97118 and VDB-99028 are related to this item. 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: 🔍
Vendor Base Score (Oracle): 5.4
Vendor Vector (Oracle): 🔍
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
12/15/2017 🔍07/17/2018 🔍
07/18/2018 🔍
07/18/2018 🔍
07/18/2018 🔍
07/18/2018 🔍
07/18/2018 🔍
04/10/2023 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2018
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-2981 (🔍)
GCVE (CVE): GCVE-0-2018-2981
GCVE (VulDB): GCVE-100-121669
SecurityFocus: 104778 - Oracle FLEXCUBE Universal Banking Multiple Security Vulnerabilities
SecurityTracker: 1041307
See also: 🔍
Entry
Created: 07/18/2018 10:06Updated: 04/10/2023 12:31
Changes: 07/18/2018 10:06 (71), 03/06/2020 16:15 (6), 04/10/2023 12:31 (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.