Is CVE-2016-5546 exploited in the wild?

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

How severe is CVE-2016-5546?

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

Which products and versions are affected?

Oracle Java SE 6u131, 7u121, 8u112; Oracle Java SE Embedded 8u111; Oracle JRockit R28.3.12.

Is there a fix for CVE-2016-5546?

A patch was published on 2017-01-19: Red Hat released security updates for affected Java packages. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-5546 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-5546?

Check whether you run Oracle Java SE, Oracle Java SE Embedded or Oracle JRockit 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-2016-5546: Oracle Java SE incorrect ECDSA signature extraction in Libraries

CVE-2016-5546 · Severity: high · CVSS 7.5 · Published 2017-01-27

A vulnerability exists in the core libraries of Oracle Java SE, Java SE Embedded, and JRockit. This flaw allows an unauthenticated attacker to remotely modify or delete critical data within the Java environment. Such an exploit could compromise the integrity of applications running on both client and server deployments, potentially leading to unauthorized system changes or data corruption.

Technologies: Oracle Java SE, Oracle Java SE Embedded, Oracle JRockit. Vendors: Oracle.

Quick answers

Is CVE-2016-5546 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5546 being exploited in the wild.
How severe is CVE-2016-5546?: High severity, with a CVSS score of 7.5, published 27 January 2017.
Which products and versions are affected?: Oracle Java SE 6u131, 7u121, 8u112; Oracle Java SE Embedded 8u111; Oracle JRockit R28.3.12.
Is there a fix for CVE-2016-5546?: A patch was published on 2017-01-19: Red Hat released security updates for affected Java packages. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-5546 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-5546?: Check whether you run Oracle Java SE, Oracle Java SE Embedded or Oracle JRockit 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

The vulnerability is located in the Libraries subcomponent of Oracle Java SE, specifically involving incorrect ECDSA signature extraction from DER input. It is an easily exploitable flaw that allows an unauthenticated attacker with network access via multiple protocols to compromise the integrity of the Java environment. The vulnerability can be triggered through sandboxed Java Web Start applications, sandboxed Java applets, or by supplying malicious data directly to affected APIs (e.g., via a web service). Successful exploitation results in unauthorized creation, deletion, or modification of data accessible to the Java runtime. The issue was addressed in Oracle's January 2017 Critical Patch Update (CPU).

Affected products

Oracle Java SE 6u131, 7u121, 8u112
Oracle Java SE Embedded 8u111
Oracle JRockit R28.3.12

Timeline

2017-01-19: patched: Red Hat released security updates for affected Java packages.
2017-01-27: disclosed: Public disclosure of the vulnerability.

References

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