Is CVE-2016-5552 exploited in the wild?

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

How severe is CVE-2016-5552?

Medium severity, with a CVSS score of 5.3, 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-5552?

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-2016-5552 attacked?

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

Am I affected by CVE-2016-5552?

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-5552: Oracle Java SE incorrect URL parsing in URLStreamHandler

CVE-2016-5552 · Severity: medium · CVSS 5.3 · Published 2017-01-27

A vulnerability in Oracle Java's networking component could allow an unauthorized person to modify or delete certain data. This affects both server-side applications and client-side tools like Java Web Start. An attacker could exploit this over a network without needing a username or password, potentially compromising the integrity of information processed by the Java environment.

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

Quick answers

Is CVE-2016-5552 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5552 being exploited in the wild.
How severe is CVE-2016-5552?: Medium severity, with a CVSS score of 5.3, 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-5552?: 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-2016-5552 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-5552?: 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

This vulnerability is classified as an incorrect URL parsing issue within the URLStreamHandler of the Networking subcomponent. It is easily exploitable by an unauthenticated attacker with network access via multiple protocols. The flaw 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 allows an attacker to perform unauthorized updates, insertions, or deletions of data accessible to the Java runtime. The issue was addressed in the Oracle January 2017 Critical Patch Update.

Affected products

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

Timeline

2017-01-19: advisory: Red Hat published security advisories RHSA-2017:0175, RHSA-2017:0176, and RHSA-2017:0177.
2017-01-27: disclosed: NVD published the CVE record.

References

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