Is CVE-2017-3439 exploited in the wild?

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

How severe is CVE-2017-3439?

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

A patch was published on 2017-01-17: Addressed in Oracle 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-3439 attacked?

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

Am I affected by CVE-2017-3439?

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-3439: Oracle E-Business Suite One-to-One Fulfillment UI vulnerability

CVE-2017-3439 · 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 perform an action, such as clicking a malicious link, and could potentially allow the attacker to impact other connected systems.

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

Quick answers

Is CVE-2017-3439 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3439 being exploited in the wild.
How severe is CVE-2017-3439?: 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-3439?: A patch was published on 2017-01-17: Addressed in Oracle 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-3439 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3439?: 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 easily exploitable flaw that allows an unauthenticated remote attacker to compromise the application via the HTTP protocol. The attack requires human interaction from a person other than the attacker (User Interaction: Required) and features a 'Changed' Scope, meaning the impact can extend beyond the immediate component to other parts of the E-Business Suite environment. Successful exploitation can result in unauthorized read access to all accessible data and unauthorized update, insert, or delete access to a subset of data. The vulnerability was addressed in the Oracle Critical Patch Update for January 2017.

Affected products

Oracle One-to-One Fulfillment (E-Business Suite) 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: advisory: Initial NVD publication
2017-01-17: patched: Addressed in Oracle January 2017 Critical Patch Update

References

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