Is CVE-2016-8302 exploited in the wild?

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

How severe is CVE-2016-8302?

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

A patch was published on 2017-01-17: Oracle released the January 2017 Critical Patch Update addressing this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-8302 attacked?

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

Am I affected by CVE-2016-8302?

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-8302: Oracle FLEXCUBE Universal Banking information disclosure in Core component

CVE-2016-8302 · Severity: medium · CVSS 4.3 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial operations and customer accounts, contains a security vulnerability in its Core subcomponent. An attacker with low-level access to the network can exploit this flaw to view sensitive banking data that they should not be authorized to see. This could lead to the exposure of confidential customer or financial information, potentially impacting the organization's data privacy compliance and reputation.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8302 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8302 being exploited in the wild.
How severe is CVE-2016-8302?: Medium severity, with a CVSS score of 4.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-8302?: A patch was published on 2017-01-17: Oracle released the January 2017 Critical Patch Update addressing this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-8302 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8302?: 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 information disclosure vulnerability (CWE-200) exists in the Core subcomponent of Oracle FLEXCUBE Universal Banking. The flaw is easily exploitable via the HTTP protocol and requires only low-privileged user credentials. A successful exploit allows a remote attacker to gain unauthorized read access to a subset of data managed by the application. 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: advisory: Initial NVD publication
2017-01-17: patched: Oracle released the January 2017 Critical Patch Update addressing this issue

References

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