Is CVE-2017-3442 exploited in the wild?

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

How severe is CVE-2017-3442?

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-3442?

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

How is CVE-2017-3442 attacked?

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

Am I affected by CVE-2017-3442?

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-3442: Oracle E-Business Suite Customer Interaction History unauthorized data access

CVE-2017-3442 · 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 manages customer contact records and communication logs. An unauthenticated attacker could exploit this flaw to gain unauthorized access to sensitive customer data or modify existing records. Successful exploitation requires a legitimate user to perform a specific action, such as clicking a malicious link, and could potentially allow the attacker to impact other connected business systems.

Technologies: Oracle Customer Interaction History. Vendors: Oracle.

Quick answers

Is CVE-2017-3442 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3442 being exploited in the wild.
How severe is CVE-2017-3442?: 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-3442?: A patch was published on 2017-01-27: Addressed in Oracle Critical Patch Update (CPU) January 2017. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-3442 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3442?: 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 (versions 12.1.1, 12.1.2, and 12.1.3). It is classified as easily exploitable and allows an unauthenticated attacker with network access via HTTP to compromise the component. The attack requires human interaction from a person other than the attacker (User Interaction: Required). The vulnerability has a 'Changed' Scope (S:C), meaning an exploit can impact components beyond the immediate Customer Interaction History environment. Successful exploitation can result in unauthorized read access to all data or unauthorized update/delete access to a subset of data. 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 and NVD publication.
2017-01-27: patched: Addressed in Oracle Critical Patch Update (CPU) January 2017.

References

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