Is CVE-2017-3236 exploited in the wild?

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

How severe is CVE-2017-3236?

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

A patch was published on 2017-01-27: Fixed in January 2017 Critical Patch Update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-3236 attacked?

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

Am I affected by CVE-2017-3236?

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-3236: Oracle FLEXCUBE Universal Banking improper input validation in Core

CVE-2017-3236 · Severity: medium · CVSS 4.7 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial transactions and customer data, contains a security vulnerability. An unauthenticated attacker could trick a legitimate user into performing an action that allows the attacker to modify, insert, or delete certain banking data. While the attacker cannot view sensitive information, this could lead to unauthorized changes in financial records or operational data.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2017-3236 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3236 being exploited in the wild.
How severe is CVE-2017-3236?: Medium severity, with a CVSS score of 4.7, 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-3236?: A patch was published on 2017-01-27: Fixed in January 2017 Critical Patch Update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-3236 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3236?: 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 (versions 11.3.0 through 12.2.0) is classified as improper input validation (CWE-20). The flaw is accessible via HTTP and does not require authentication, though it does require human interaction from a legitimate user (UI:R) to be successful. The vulnerability has a 'Changed' scope (S:C), meaning an exploit can impact components beyond the immediate banking application. Successful exploitation allows an attacker to perform unauthorized updates, insertions, or deletions of data, impacting the integrity of the system. Oracle addressed this in the January 2017 Critical Patch Update.

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 by Oracle
2017-01-27: patched: Fixed in January 2017 Critical Patch Update

References

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