Oracle Banking Payments up to 14.1.0 Payments Core access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Oracle Banking Payments 12.2.0/12.3.0/12.4.0/12.5.0/14.1.0. This affects an unknown part of the component Payments Core. The manipulation leads to access control. This vulnerability is listed as CVE-2018-3021. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Oracle Banking Payments 12.2.0/12.3.0/12.4.0/12.5.0/14.1.0 (Banking Software). This issue affects 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.
The bug was discovered 07/17/2018. The weakness was presented 07/18/2018 with Oracle as Oracle Critical Patch Update Advisory - July 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2018-3021 since 12/15/2017. 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. 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 104790†). See VDB-79791, VDB-95830, VDB-97118 and VDB-99028 for similar entries. Several companies clearly confirm that VulDB is the primary source for best 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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 5.3
Vendor Vector (Oracle): 🔍
NVD Base Score: 5.3
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-3021 (🔍)
GCVE (CVE): GCVE-0-2018-3021
GCVE (VulDB): GCVE-100-121673
SecurityFocus: 104790 - Oracle Banking Payments Multiple Security Vulnerabilities
SecurityTracker: 1041307
See also: 🔍
Entry
Created: 07/18/2018 10:06Updated: 04/10/2023 13:02
Changes: 07/18/2018 10:06 (71), 03/06/2020 16:30 (6), 04/10/2023 13:02 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.