CVE-2017-10285: Critical severity oracle java se 7 vulnerability
A flaw was found in the privileged code used to handle unreferenced objects in the Target class in the RMI component of OpenJDK. An untrusted Java application or applet could use this flaw to bypass Java sandbox restrictions.
Other sources
Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). Supported versions that are affected are Java SE: 6u161, 7u151, 8u144 and 9; Java SE Embedded: 8u144. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, Java SE Embedded, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.0 Base Score 9.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-10285?
CVE-2017-10285 is considered to have high severity due to its potential to allow untrusted Java applications to bypass sandbox restrictions.
How do I fix CVE-2017-10285?
To fix CVE-2017-10285, you should update your Java SE or Java Runtime Environment to the latest version that addresses this vulnerability.
Which versions are affected by CVE-2017-10285?
CVE-2017-10285 affects multiple versions of Oracle JDK and JRE, specifically 1.6.0-update161, 1.7.0-update151, and 1.8.0-update144, among others.
What could happen if CVE-2017-10285 is exploited?
If exploited, CVE-2017-10285 could allow an attacker to execute untrusted code with elevated privileges, compromising the security of the host system.
Is there a workaround for CVE-2017-10285?
While updating is the most effective solution for CVE-2017-10285, restricting the execution of untrusted Java applications may serve as a temporary workaround.