Is CVE-2017-3425 exploited in the wild?

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

How severe is CVE-2017-3425?

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

Which products and versions are affected?

Oracle One-To-One Fulfillment 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-3425?

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

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

Am I affected by CVE-2017-3425?

Check whether you run Oracle One-To-One Fulfillment 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-3425: Oracle E-Business Suite One-to-One Fulfillment Security Bypass in UI

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

A vulnerability exists in the Oracle One-to-One Fulfillment component of the Oracle E-Business Suite, which is used for managing high-volume personalized communications. An unauthenticated attacker could exploit this flaw to gain unauthorized access to sensitive business data or modify existing records. Successful exploitation requires a legitimate user to interact with a malicious link or page, potentially allowing the attacker to compromise the application and impact connected systems.

Technologies: Oracle One-To-One Fulfillment. Vendors: Oracle.

Quick answers

Is CVE-2017-3425 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3425 being exploited in the wild.
How severe is CVE-2017-3425?: High severity, with a CVSS score of 8.2, published 27 January 2017.
Which products and versions are affected?: Oracle One-To-One Fulfillment 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-3425?: 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-3425 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3425?: Check whether you run Oracle One-To-One Fulfillment 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 One-to-One Fulfillment within Oracle E-Business Suite. It is an unauthenticated, network-based attack vector (HTTP) that requires human interaction from a person other than the attacker (UI:R). The vulnerability has a 'Changed' scope (S:C), meaning an exploit can impact components beyond the immediate One-to-One Fulfillment environment. Attackers can achieve unauthorized access to all accessible data (Confidentiality: High) and perform unauthorized updates or deletions of some data (Integrity: Low). Affected versions include 12.1.1 through 12.2.6.

Affected products

Oracle One-to-One Fulfillment 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 (CPU) released

References

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