Is CVE-2017-3253 exploited in the wild?

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

How severe is CVE-2017-3253?

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-2017-3253?

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-2017-3253 attacked?

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

Am I affected by CVE-2017-3253?

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-2017-3253: Oracle Java SE denial of service in 2D component

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

A vulnerability in the 2D graphics component of Oracle Java can allow a remote attacker to crash or freeze a Java-based application. This affects both client-side applications, like web applets, and server-side web services. An exploit could lead to a complete denial of service, disrupting business operations and application availability.

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

Quick answers

Is CVE-2017-3253 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3253 being exploited in the wild.
How severe is CVE-2017-3253?: 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-2017-3253?: 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-2017-3253 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-3253?: 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 2D subcomponent of the Java Runtime Environment, specifically within the imageio PNGImageReader. The root cause involves a failure to properly honor the 'ignoreMetadata' flag when processing iTXt and zTXt chunks in PNG images. An unauthenticated attacker can exploit this by providing specially crafted data to Java APIs (e.g., via a web service) or through sandboxed Java Web Start applications and applets. Successful exploitation results in a complete denial of service (hang or crash) of the Java process. Patches were released in the January 2017 Oracle Critical Patch Update (e.g., Java SE 8u121).

Affected products

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

Timeline

2017-01-17: advisory: Oracle Critical Patch Update released
2017-01-19: patched: Red Hat released security updates for affected Java packages
2017-01-27: disclosed: NVD publication date

References

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