Is CVE-2017-3235 exploited in the wild?

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

How severe is CVE-2017-3235?

Low severity, with a CVSS score of 3.5, 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-2017-3235?

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-2017-3235 attacked?

It is attacked with physical access, in a network appliance.

Am I affected by CVE-2017-3235?

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-2017-3235: Oracle FLEXCUBE Universal Banking data manipulation via physical access

CVE-2017-3235 · Severity: low · CVSS 3.5 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial transactions and customer data, contains a vulnerability that can be exploited by someone with physical access to the system. An unauthorized person could potentially read, modify, or delete sensitive banking data. While the risk is limited to those with physical proximity to the hardware, it could lead to unauthorized data manipulation or information disclosure.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2017-3235 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3235 being exploited in the wild.
How severe is CVE-2017-3235?: Low severity, with a CVSS score of 3.5, 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-2017-3235?: 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-2017-3235 attacked?: It is attacked with physical access, in a network appliance.
Am I affected by CVE-2017-3235?: 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 for unauthorized data access and modification. The flaw is categorized as easily exploitable but requires the 'Physical' attack vector, meaning the attacker must have physical access to the device or infrastructure where the software is running. Successful exploitation enables an attacker to perform unauthorized read, update, insert, or delete operations on a subset of the application's data. The vulnerability affects multiple versions ranging from 11.3.0 to 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: disclosed
2017-01-27: advisory: Oracle Critical Patch Update published

References

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