Is CVE-2016-8313 exploited in the wild?

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

How severe is CVE-2016-8313?

Medium severity, with a CVSS score of 4.1, published 27 January 2017.

Which products and versions are affected?

Oracle Flexcube Private Banking 2.0.1, 2.2.0, 12.0.1.

Is there a fix for CVE-2016-8313?

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

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

Am I affected by CVE-2016-8313?

Check whether you run Oracle Flexcube Private 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-8313: Oracle FLEXCUBE Private Banking information disclosure in Product Search

CVE-2016-8313 · Severity: medium · CVSS 4.1 · Published 2017-01-27

Oracle FLEXCUBE Private Banking, a platform used by financial institutions to manage wealth and investment services, contains a security vulnerability in its search functionality. A low-privileged user could potentially gain unauthorized access to sensitive banking data by tricking another user into performing a specific action. While the direct impact is limited to reading a subset of data, the breach could potentially affect other integrated systems.

Technologies: Oracle Flexcube Private Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8313 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8313 being exploited in the wild.
How severe is CVE-2016-8313?: Medium severity, with a CVSS score of 4.1, published 27 January 2017.
Which products and versions are affected?: Oracle Flexcube Private Banking 2.0.1, 2.2.0, 12.0.1.
Is there a fix for CVE-2016-8313?: 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-8313 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8313?: Check whether you run Oracle Flexcube Private 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 Product / Instrument Search subcomponent of Oracle FLEXCUBE Private Banking (versions 2.0.1, 2.2.0, and 12.0.1) allows for unauthorized information disclosure. The flaw is classified as CWE-200 (Exposure of Sensitive Information) and is exploitable via the HTTP protocol. An attacker with low privileges can trigger the vulnerability, but successful exploitation requires human interaction from a victim (User Interaction: Required). The vulnerability has a 'Scope: Changed' (S:C) designation, indicating that an attack on this component may impact other security domains or products. The primary impact is a partial loss of confidentiality (C:L).

Affected products

Oracle FLEXCUBE Private Banking 2.0.1, 2.2.0, 12.0.1

Timeline

2017-01-27: advisory: Initial NVD publication date
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.