Is CVE-2016-8319 exploited in the wild?

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

How severe is CVE-2016-8319?

Medium severity, with a CVSS score of 6.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-8319?

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

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

Am I affected by CVE-2016-8319?

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-8319: Oracle FLEXCUBE Investor Servicing improper access control in Core

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

Oracle FLEXCUBE Investor Servicing, a financial application used for managing investment funds and transfer agency operations, contains a security vulnerability in its core component. An unauthenticated attacker could exploit this flaw to gain unauthorized access to view, modify, or delete sensitive financial data. Successful exploitation requires a legitimate user to perform a specific action, such as clicking a malicious link, and could potentially impact other integrated business systems.

Technologies: Oracle Flexcube Investor Servicing. Vendors: Oracle.

Quick answers

Is CVE-2016-8319 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8319 being exploited in the wild.
How severe is CVE-2016-8319?: Medium severity, with a CVSS score of 6.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-8319?: 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-8319 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8319?: 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 in the Core subcomponent of Oracle FLEXCUBE Investor Servicing (versions 12.0.1 through 12.3.0) allows an unauthenticated remote attacker to impact the system via HTTP. The vulnerability is classified under improper access control (CWE-284) and requires human interaction from a person other than the attacker (User Interaction: Required). Successful exploitation allows unauthorized read, update, insert, or delete access to a subset of accessible data. Notably, the vulnerability has a 'Changed' scope (S:C), indicating that an attack on FLEXCUBE could potentially impact additional integrated products or the underlying environment. Oracle addressed this in the January 2017 Critical Patch Update.

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: disclosed
2017-01-27: advisory: Oracle January 2017 Critical Patch Update published

References

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