Oracle FLEXCUBE Private Banking 2.0.0/2.0.1/2.2.0.1/12.0.1 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oracle FLEXCUBE Private Banking 2.0.0/2.0.1/2.2.0.1/12.0.1. It has been classified as critical. Affected is an unknown function. Performing a manipulation results in access control. This vulnerability is reported as CVE-2017-3475. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in Oracle FLEXCUBE Private Banking 2.0.0/2.0.1/2.2.0.1/12.0.1 (Banking Software). It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on availability.
The bug was discovered 04/18/2017. The weakness was disclosed 04/19/2017 with Oracle as Oracle Critical Patch Update Advisory - April 2017 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2017-3475 since 12/06/2016. It is possible to initiate the attack remotely. The requirement for exploitation is a 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 97816†). The entries VDB-95628, VDB-95669, VDB-95670 and VDB-95704 are pretty similar. 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.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 5.0
Vendor Vector (Oracle): 🔍
NVD Base Score: 5.0
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/06/2016 🔍04/18/2017 🔍
04/18/2017 🔍
04/19/2017 🔍
04/19/2017 🔍
04/19/2017 🔍
04/24/2017 🔍
12/19/2020 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - April 2017
Researcher: Oracle
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-3475 (🔍)
GCVE (CVE): GCVE-0-2017-3475
GCVE (VulDB): GCVE-100-100077
SecurityFocus: 97816 - Oracle FLEXCUBE Private Banking CVE-2017-3475 Remote Security Vulnerability
OSVDB: - CVE-2017-3475 - Oracle - Financial Services Applications - Unspecified Issue
SecurityTracker: 1038304
See also: 🔍
Entry
Created: 04/19/2017 19:11Updated: 12/19/2020 15:52
Changes: 04/19/2017 19:11 (71), 09/16/2020 17:39 (7), 12/19/2020 15:47 (4), 12/19/2020 15:52 (1)
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.