Is CVE-2017-3440 exploited in the wild?

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

How severe is CVE-2017-3440?

High severity, with a CVSS score of 8.2, published 27 January 2017.

Which products and versions are affected?

Oracle Customer Interaction History 12.1.1, 12.1.2, 12.1.3.

Is there a fix for CVE-2017-3440?

A patch was published on 2017-01-27: Fix released 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-3440 attacked?

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

Am I affected by CVE-2017-3440?

Check whether you run Oracle Customer Interaction History 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-3440: Oracle E-Business Suite vulnerability in Customer Interaction History UI

CVE-2017-3440 · Severity: high · CVSS 8.2 · Published 2017-01-27

A vulnerability exists in the Oracle Customer Interaction History component of the Oracle E-Business Suite, which is used by businesses to manage and track customer communications. An unauthenticated attacker could exploit this flaw to gain unauthorized access to sensitive customer data or modify records, potentially leading to data breaches or loss of data integrity. Exploitation requires a legitimate user to perform a specific action, such as clicking a malicious link, and the impact can extend beyond the interaction history to other connected business systems.

Technologies: Oracle Customer Interaction History. Vendors: Oracle.

Quick answers

Is CVE-2017-3440 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3440 being exploited in the wild.
How severe is CVE-2017-3440?: High severity, with a CVSS score of 8.2, published 27 January 2017.
Which products and versions are affected?: Oracle Customer Interaction History 12.1.1, 12.1.2, 12.1.3.
Is there a fix for CVE-2017-3440?: A patch was published on 2017-01-27: Fix released 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-3440 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3440?: Check whether you run Oracle Customer Interaction History 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

This vulnerability affects the User Interface subcomponent of Oracle Customer Interaction History in Oracle E-Business Suite versions 12.1.1, 12.1.2, and 12.1.3. It is an easily exploitable flaw that allows an unauthenticated attacker with network access via HTTP to compromise the system. The attack requires user interaction (UI:R) from a person other than the attacker. The vulnerability has a 'Changed' scope (S:C), meaning a successful exploit can impact components beyond the immediate Customer Interaction History environment. Attackers can achieve high confidentiality impact and partial integrity impact, resulting in unauthorized access to all accessible data or the ability to update and delete certain records. Oracle addressed this in the January 2017 Critical Patch Update.

Affected products

Oracle Customer Interaction History 12.1.1, 12.1.2, 12.1.3

Timeline

2017-01-27: advisory: Initial disclosure by Oracle
2017-01-27: patched: Fix released in January 2017 Critical Patch Update

References

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