Is CVE-2016-8307 exploited in the wild?

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

How severe is CVE-2016-8307?

Medium severity, with a CVSS score of 5.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-8307?

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

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

Am I affected by CVE-2016-8307?

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-8307: Oracle FLEXCUBE Universal Banking improper access control in Core

CVE-2016-8307 · Severity: medium · CVSS 5.3 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used by financial institutions to manage retail and corporate banking operations, contains a security vulnerability. An unauthenticated attacker can exploit this flaw over the network to gain unauthorized access to sensitive banking data. This could lead to the exposure of confidential customer or financial information, potentially impacting the organization's regulatory compliance and reputation.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8307 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8307 being exploited in the wild.
How severe is CVE-2016-8307?: Medium severity, with a CVSS score of 5.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-8307?: 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-8307 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8307?: 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 (classified as improper access control, CWE-284) allows for unauthorized data retrieval. The flaw is easily exploitable by an unauthenticated attacker with network access via HTTP. Successful exploitation results in unauthorized read access to a subset of FLEXCUBE Universal Banking accessible data, impacting confidentiality. Affected versions include 11.3.0 through 12.2.0. Oracle addressed this issue in the January 2017 Critical Patch Update.

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 January 2017 Critical Patch Update released

References

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