Is CVE-2017-3400 exploited in the wild?

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

How severe is CVE-2017-3400?

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

Which products and versions are affected?

Oracle Advanced Outbound Telephony 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6.

Is there a fix for CVE-2017-3400?

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

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

Am I affected by CVE-2017-3400?

Check whether you run Oracle Advanced Outbound Telephony 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-3400: Oracle Advanced Outbound Telephony UI vulnerability in E-Business Suite

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

A vulnerability exists in the user interface of Oracle's Advanced Outbound Telephony, a component of the E-Business Suite used for managing high-volume customer communications. An attacker could exploit this flaw to gain unauthorized access to sensitive business data or modify records, potentially impacting other integrated Oracle products. Successful exploitation requires a legitimate user to interact with a malicious link or page, which could lead to a significant breach of confidentiality and data integrity.

Technologies: Oracle Advanced Outbound Telephony. Vendors: Oracle.

Quick answers

Is CVE-2017-3400 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3400 being exploited in the wild.
How severe is CVE-2017-3400?: High severity, with a CVSS score of 8.2, published 27 January 2017.
Which products and versions are affected?: Oracle Advanced Outbound Telephony 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6.
Is there a fix for CVE-2017-3400?: 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-3400 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3400?: Check whether you run Oracle Advanced Outbound Telephony 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 Advanced Outbound Telephony within the Oracle E-Business Suite. It is an unauthenticated, network-based attack vector via HTTP that requires human interaction (User Interaction: Required) from a person other than the attacker. The vulnerability is characterized by a 'Changed' scope (S:C), meaning an exploit can impact components beyond the immediate software. Attackers can achieve unauthorized access to all accessible data (Confidentiality: High) and perform unauthorized updates or deletions of some data (Integrity: Low). The issue is addressed in the Oracle Critical Patch Update for January 2017.

Affected products

Oracle Advanced Outbound Telephony 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6

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.