Is CVE-2016-8310 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-8310 being exploited in the wild.

How severe is CVE-2016-8310?

High severity, with a CVSS score of 7.3, published 27 January 2017.

Which products and versions are affected?

Oracle Flexcube Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0.

Is there a fix for CVE-2016-8310?

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-8310 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2016-8310?

Check whether you run Oracle Flexcube Universal 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.

CVE-2016-8310: Oracle FLEXCUBE Universal Banking security bypass in Core component

CVE-2016-8310 · Severity: high · CVSS 7.3 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial transactions and customer accounts, contains a security vulnerability in its Core subcomponent. An unauthenticated attacker can exploit this over the network to view, modify, or delete sensitive banking data. This could lead to unauthorized financial records changes or a partial disruption of banking services.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8310 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8310 being exploited in the wild.
How severe is CVE-2016-8310?: High severity, with a CVSS score of 7.3, published 27 January 2017.
Which products and versions are affected?: Oracle Flexcube Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0.
Is there a fix for CVE-2016-8310?: 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-8310 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8310?: Check whether you run Oracle Flexcube Universal 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

A vulnerability in the Core subcomponent of Oracle FLEXCUBE Universal Banking allows an unauthenticated attacker with network access via HTTP to compromise the system. The flaw is classified under CWE-254 (Security Features) and is considered easily exploitable without user interaction. An attacker can achieve unauthorized read, update, insert, or delete access to a subset of the application's data. Additionally, the vulnerability can be used to cause a partial denial of service (DoS). The issue affects multiple versions ranging from 11.3.0 to 12.2.0 and was addressed in the Oracle Critical Patch Update for January 2017.

Affected products

Oracle FLEXCUBE Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0

Timeline

2017-01-27: disclosed
2017-01-27: advisory: Oracle Critical Patch Update published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.