Is CVE-2016-5509 exploited in the wild?

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

How severe is CVE-2016-5509?

Low severity, with a CVSS score of 3.1, published 27 January 2017.

Which products and versions are affected?

Oracle Flexcube Investor Servicing 12.0.1, 12.0.2, 12.0.4, 12.1.0, 12.3.0.

Is there a fix for CVE-2016-5509?

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

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

Am I affected by CVE-2016-5509?

Check whether you run Oracle Flexcube Investor Servicing 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-5509: Oracle FLEXCUBE Investor Servicing information disclosure in Core

CVE-2016-5509 · Severity: low · CVSS 3.1 · Published 2017-01-27

Oracle FLEXCUBE Investor Servicing is a financial services platform used for managing investment portfolios and investor records. A vulnerability in the 'Core' component could allow an authorized user with low-level access to view sensitive data they are not supposed to see. While the risk is limited to specific subsets of data and requires specific conditions to exploit, it could lead to unauthorized disclosure of financial information.

Technologies: Oracle Flexcube Investor Servicing. Vendors: Oracle.

Quick answers

Is CVE-2016-5509 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5509 being exploited in the wild.
How severe is CVE-2016-5509?: Low severity, with a CVSS score of 3.1, published 27 January 2017.
Which products and versions are affected?: Oracle Flexcube Investor Servicing 12.0.1, 12.0.2, 12.0.4, 12.1.0, 12.3.0.
Is there a fix for CVE-2016-5509?: 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-5509 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5509?: Check whether you run Oracle Flexcube Investor Servicing 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 exists in the Core subcomponent of Oracle FLEXCUBE Investor Servicing (versions 12.0.1 through 12.3.0). The flaw is accessible via the HTTP protocol and requires the attacker to have low-privileged credentials. Exploitation is considered difficult (High Attack Complexity) but can result in unauthorized read access to a subset of data within the application. The vulnerability was addressed in the Oracle Critical Patch Update for January 2017.

Affected products

Oracle FLEXCUBE Investor Servicing 12.0.1, 12.0.2, 12.0.4, 12.1.0, 12.3.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.