Is CVE-2016-8303 exploited in the wild?

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

How severe is CVE-2016-8303?

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

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

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

Am I affected by CVE-2016-8303?

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-8303: Oracle FLEXCUBE Universal Banking data manipulation in Core

CVE-2016-8303 · Severity: medium · CVSS 6.1 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial operations and customer data, contains a security vulnerability in its Core subcomponent. An unauthenticated attacker could exploit this flaw to gain unauthorized access to view, modify, or delete sensitive banking data. Successful exploitation requires a legitimate user to perform a specific action, such as clicking a malicious link, and could potentially impact other integrated systems.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

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

A vulnerability in the Core subcomponent of Oracle FLEXCUBE Universal Banking allows unauthenticated attackers with network access via HTTP to compromise the system. The flaw is characterized by a 'Changed' scope in CVSS metrics, suggesting it may be a Cross-Site Scripting (XSS) or similar injection vulnerability that allows an attacker to impact components beyond the immediate application. Successful exploitation requires user interaction (UI:R) from a person other than the attacker. If successful, the attacker can achieve unauthorized read access to a subset of data and unauthorized update, insert, or delete access to some accessible data. The vulnerability affects versions 11.3.0 through 12.2.0 and was addressed in the Oracle Critical Patch Update for January 2017.

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 disclosure in Oracle Critical Patch Update
2017-01-27: disclosed

References

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