Is CVE-2016-5623 exploited in the wild?

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

How severe is CVE-2016-5623?

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

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

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

Am I affected by CVE-2016-5623?

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-5623: Oracle FLEXCUBE Private Banking data manipulation in Product Search

CVE-2016-5623 · Severity: medium · CVSS 5.4 · 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. An authorized user with low-level permissions could exploit this flaw to view, modify, or delete certain banking data they should not have access to. This could lead to unauthorized changes to financial records or the exposure of sensitive client information.

Technologies: Oracle Flexcube Private Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-5623 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5623 being exploited in the wild.
How severe is CVE-2016-5623?: Medium severity, with a CVSS score of 5.4, 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-5623?: 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-5623 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5623?: 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 exists in the Product / Instrument Search subcomponent of Oracle FLEXCUBE Private Banking (versions 2.0.1, 2.2.0, and 12.0.1). The flaw is categorized under CWE-254 (Security Features) and allows a low-privileged attacker with network access via HTTP to compromise the system. Successful exploitation enables the attacker to perform unauthorized update, insert, or delete operations on a subset of accessible data, as well as unauthorized read access. The attack does not require user interaction. Oracle addressed this in the January 2017 Critical Patch Update.

Affected products

Oracle FLEXCUBE Private Banking 2.0.1, 2.2.0, 12.0.1

Timeline

2017-01-27: disclosed
2017-01-27: advisory: Oracle January 2017 Critical Patch Update released

References

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