Quick answers
- Is CVE-2016-8314 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-8314 being exploited in the wild.
- How severe is CVE-2016-8314?
- Low severity, with a CVSS score of 3.1, published 27 January 2017.
- Which products and versions are affected?
- Oracle Flexcube Core Banking 5.1.0, 5.2.0, 11.5.0.
- Is there a fix for CVE-2016-8314?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2016-8314 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2016-8314?
- Check whether you run Oracle Flexcube Core Banking at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability affects the Core subcomponent of Oracle FLEXCUBE Core Banking versions 5.1.0, 5.2.0, and 11.5.0. It is classified as difficult to exploit (High Attack Complexity) and requires the attacker to have low-level authenticated privileges. The attack vector is network-based via HTTP. Successful exploitation results in a partial loss of confidentiality, allowing the attacker to read a subset of data they should not have access to. The vulnerability was addressed in the Oracle Critical Patch Update for January 2017.
Affected products
- Oracle FLEXCUBE Core Banking 5.1.0, 5.2.0, 11.5.0
Timeline
- 2017-01-27: disclosed
- 2017-01-27: advisory: Oracle Critical Patch Update published