CVE-2017-10067: High severity oracle java se 7 vulnerability
It was discovered that the JAR (Java ARchive) verifier in the Security component of OpenJDK did not correctly handle files inside archives with missing digest. An attacker could possibly use this flaw to manipulate content of a singed JAR, bypassing intended verification.
Other sources
Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Security). Supported versions that are affected are Java SE: 6u151, 7u141 and 8u131. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Java SE. 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 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-10067?
CVE-2017-10067 is considered a difficult-to-exploit vulnerability that affects certain versions of Oracle Java SE and JRE.
How do I fix CVE-2017-10067?
To fix CVE-2017-10067, update your Oracle Java SE or JRE to a version that is not affected, such as the latest version released after 6u151, 7u141, and 8u131.
Which versions of Java are affected by CVE-2017-10067?
CVE-2017-10067 affects Java SE versions 6u151, 7u141, and 8u131.
Can CVE-2017-10067 be exploited remotely?
Yes, CVE-2017-10067 can be exploited by an unauthenticated attacker with network access via multiple protocols.
Is CVE-2017-10067 fixed in the latest Java releases?
Yes, CVE-2017-10067 has been addressed in later updates of the affected Java SE versions.