Is CVE-2016-8311 exploited in the wild?

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

How severe is CVE-2016-8311?

Medium severity, with a CVSS score of 6.5, 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-8311?

A patch was published on 2017-01-17: Addressed in Oracle Critical Patch Update (CPU) January 2017 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-8311 attacked?

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

Am I affected by CVE-2016-8311?

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

CVE-2016-8311 · Severity: medium · CVSS 6.5 · Published 2017-01-27

A vulnerability in Oracle FLEXCUBE Universal Banking, a core banking platform, could allow an authorized user with low-level permissions to access sensitive financial data. An attacker could exploit this to view critical information they are not supposed to see, potentially compromising customer privacy and regulatory compliance. The issue affects the 'Core' subcomponent of the banking suite.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8311 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8311 being exploited in the wild.
How severe is CVE-2016-8311?: Medium severity, with a CVSS score of 6.5, 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-8311?: A patch was published on 2017-01-17: Addressed in Oracle Critical Patch Update (CPU) January 2017 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-8311 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8311?: 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

An improper access control vulnerability (CWE-284) exists in the Core subcomponent of Oracle FLEXCUBE Universal Banking. The flaw is easily exploitable by a low-privileged attacker with network access via HTTP. Successful exploitation allows the attacker to bypass intended security restrictions to gain unauthorized access to critical data or complete access to all data accessible by the FLEXCUBE component. The vulnerability 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: advisory: Initial NVD publication
2017-01-17: patched: Addressed in Oracle Critical Patch Update (CPU) January 2017

References

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