CVE-2016-8307
First published: Fri Jan 27 2017(Updated: )
Vulnerability in the Oracle FLEXCUBE Universal Banking component of Oracle Financial Services Applications (subcomponent: Core). Supported versions that are affected are 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0 and 12.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle FLEXCUBE Universal Banking. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle FLEXCUBE Universal Banking accessible data. CVSS v3.0 Base Score 5.3 (Confidentiality impacts).
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle FLEXCUBE Universal Banking | =11.3.0 | |
| Oracle FLEXCUBE Universal Banking | =11.4.0 | |
| Oracle FLEXCUBE Universal Banking | =12.0.1 | |
| Oracle FLEXCUBE Universal Banking | =12.0.2 | |
| Oracle FLEXCUBE Universal Banking | =12.0.3 | |
| Oracle FLEXCUBE Universal Banking | =12.1.0 | |
| Oracle FLEXCUBE Universal Banking | =12.2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-8307?
CVE-2016-8307 is classified as an easily exploitable vulnerability that allows unauthenticated access, posing significant risk to affected systems.
Which versions of Oracle FLEXCUBE Universal Banking are affected by CVE-2016-8307?
CVE-2016-8307 affects Oracle FLEXCUBE Universal Banking versions 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0 and 12.2.0.
How can I remediate CVE-2016-8307?
To fix CVE-2016-8307, apply the latest security patches provided by Oracle for the affected versions of FLEXCUBE Universal Banking.
What impact does CVE-2016-8307 have on data security?
CVE-2016-8307 can lead to unauthorized data access and potential data breaches, compromising sensitive financial information.
Is there a workaround for CVE-2016-8307?
There are no known effective workarounds for CVE-2016-8307; patching is the recommended solution.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- vendor/oracle
- canonical/oracle flexcube universal banking
- version/oracle flexcube universal banking/11.3.0
- version/oracle flexcube universal banking/11.4.0
- version/oracle flexcube universal banking/12.0.1
- version/oracle flexcube universal banking/12.0.2
- version/oracle flexcube universal banking/12.0.3
- version/oracle flexcube universal banking/12.1.0
- version/oracle flexcube universal banking/12.2.0