Is CVE-2017-3415 exploited in the wild?

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

How severe is CVE-2017-3415?

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

Which products and versions are affected?

Oracle Universal Work Queue 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-3415?

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

How is CVE-2017-3415 attacked?

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

Am I affected by CVE-2017-3415?

Check whether you run Oracle Universal Work Queue 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-3415: Oracle Universal Work Queue unauthorized data access in User Interface

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

A vulnerability exists in the Oracle Universal Work Queue component of the Oracle E-Business Suite, which is used by organizations to manage and distribute tasks across different departments. 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 a specific action, such as clicking a malicious link, and could potentially allow the attacker to impact other integrated business systems.

Technologies: Oracle Universal Work Queue. Vendors: Oracle.

Quick answers

Is CVE-2017-3415 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3415 being exploited in the wild.
How severe is CVE-2017-3415?: High severity, with a CVSS score of 8.2, published 27 January 2017.
Which products and versions are affected?: Oracle Universal Work Queue 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-3415?: A patch was published on 2017-01-27: Fixed in Oracle Critical Patch Update January 2017 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-3415 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-3415?: Check whether you run Oracle Universal Work Queue 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 Universal Work Queue within Oracle E-Business Suite. It is an unauthenticated, network-based attack vector via HTTP. The vulnerability has a CVSS 3.0 base score of 8.2, characterized by high confidentiality impact and low integrity impact. A key precondition is human interaction from a person other than the attacker (UI:R). The 'Scope' metric is changed (S:C), indicating that a successful exploit can impact components beyond the immediate security scope of the Universal Work Queue. Attackers can achieve unauthorized access to all accessible data or perform unauthorized updates, inserts, or deletes on a subset of data. Oracle addressed this in the January 2017 Critical Patch Update.

Affected products

Oracle Universal Work Queue 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: patched: Fixed in Oracle Critical Patch Update January 2017

References

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