First published: Tue Jan 17 2017(Updated: )
It was discovered that the RMI registry and DCG (Distributed Garbage Collector) implementations in the RMI component of OpenJDK performed deserialization of untrusted inputs. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle JDK 6 | =1.6-update_131 | |
Oracle JDK 6 | =1.7-update_121 | |
Oracle JDK 6 | =1.8-update_111 | |
Oracle JDK 6 | =1.8-update_112 | |
Oracle Java Runtime Environment (JRE) | =1.6-update_131 | |
Oracle Java Runtime Environment (JRE) | =1.7-update_121 | |
Oracle Java Runtime Environment (JRE) | =1.8-update_111 | |
Oracle Java Runtime Environment (JRE) | =1.8-update_112 | |
BEA JRockit | =r28.3.12 | |
debian/openjdk-8 | 8u442-ga-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3241 has been classified with a high severity level due to the potential for remote code execution.
To fix CVE-2017-3241, update your OpenJDK or Oracle JDK to a version that includes the security patch, such as Oracle JDK 8u442 or later.
CVE-2017-3241 affects specific versions of Oracle JDK and JRE, including 1.6-update_131, 1.7-update_121, and 1.8-update_111 and 1.8-update_112.
Yes, CVE-2017-3241 can potentially allow a remote attacker to execute arbitrary code, leading to unauthorized access.
A temporary workaround for CVE-2017-3241 is to disable RMI or restrict access to the RMI registry until you can apply a patch.