Is CVE-2016-8324 exploited in the wild?

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

How severe is CVE-2016-8324?

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

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

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

Am I affected by CVE-2016-8324?

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.

CVE-2016-8324: Oracle FLEXCUBE Core Banking improper access control in Core subcomponent

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

A vulnerability exists in Oracle FLEXCUBE Core Banking, a platform used by financial institutions to manage core banking operations and customer transactions. An unauthenticated attacker can exploit this flaw over the network to gain unauthorized access to sensitive banking data. While the attacker cannot modify data or shut down the system, the exposure of confidential information could lead to regulatory compliance issues and reputational damage.

Technologies: Oracle Flexcube Core Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8324 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8324 being exploited in the wild.
How severe is CVE-2016-8324?: Medium severity, with a CVSS score of 5.3, 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-8324?: 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-8324 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8324?: 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

The vulnerability is classified as improper access control (CWE-284) within the 'Core' subcomponent of Oracle FLEXCUBE Core Banking. It is easily exploitable by an unauthenticated attacker with network access via HTTP. The flaw allows for the unauthorized retrieval of a subset of data accessible to the FLEXCUBE component. The impact is limited to confidentiality, with no reported impact on data integrity or system availability. Affected versions include 5.1.0, 5.2.0, and 11.5.0. Oracle addressed this in the January 2017 Critical Patch Update.

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

References

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