Is CVE-2017-3241 exploited in the wild?

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

How severe is CVE-2017-3241?

Critical severity, with a CVSS score of 9, 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-3241?

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

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

Am I affected by CVE-2017-3241?

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-3241: Oracle Java SE untrusted input deserialization in RMI

CVE-2017-3241 · Severity: critical · CVSS 9 · Published 2017-01-27

A critical vulnerability exists in the Remote Method Invocation (RMI) component of Oracle Java. This component allows different Java applications to communicate with each other over a network. An attacker could exploit this flaw to take complete control of the affected system, potentially leading to data theft, service disruption, or unauthorized access to corporate resources.

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

Quick answers

Is CVE-2017-3241 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3241 being exploited in the wild.
How severe is CVE-2017-3241?: Critical severity, with a CVSS score of 9, 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-3241?: 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-2017-3241 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-3241?: 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 an untrusted input deserialization flaw within the RMI registry and Distributed Garbage Collection (DGC) subcomponents of Oracle Java. An unauthenticated attacker can exploit this by sending specially crafted malicious data over the network to an exposed RMI service. While the vulnerability is considered difficult to exploit, a successful attack results in a complete takeover of the Java Runtime Environment (JRE) and can significantly impact other products relying on the affected Java installation. The vulnerability is specifically exploitable through APIs in the RMI component, such as through web services, but does not affect untrusted Java Web Start applications or applets. Patches were released 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 security advisory issued
2017-01-27: disclosed: NVD publication date

References

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