Oracle Banking Payments up to 14.1.0 Payments Core access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oracle Banking Payments 12.2.0/12.3.0/12.4.0/12.5.0/14.1.0. It has been declared as critical. This vulnerability affects unknown code of the component Payments Core. Such manipulation leads to access control. This vulnerability is uniquely identified as CVE-2018-2896. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Oracle Banking Payments 12.2.0/12.3.0/12.4.0/12.5.0/14.1.0 (Banking Software). It has been rated as critical. Affected by this issue is some unknown processing of the component Payments Core. 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 bug was discovered 07/17/2018. The weakness was disclosed 07/18/2018 with Oracle as Oracle Critical Patch Update Advisory - July 2018 as confirmed advisory (Website). The advisory is shared for download at oracle.com. This vulnerability is handled as CVE-2018-2896 since 12/15/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
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 104790†). The entries VDB-79791, VDB-95830, VDB-97118 and VDB-99028 are pretty similar. Once again VulDB remains the best source for vulnerability data.
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: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.1
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 6.1
Vendor Vector (Oracle): 🔍
NVD Base Score: 6.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: 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/17/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-2896 (🔍)
GCVE (CVE): GCVE-0-2018-2896
GCVE (VulDB): GCVE-100-121652
SecurityFocus: 104790 - Oracle Banking Payments Multiple Security Vulnerabilities
SecurityTracker: 1041307
See also: 🔍
Entry
Created: 07/18/2018 10:06Updated: 04/10/2023 10:36
Changes: 07/18/2018 10:06 (71), 03/06/2020 15:24 (6), 04/10/2023 10:36 (5)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.