CVE-2017-3512: High severity Oracle JDK vulnerability

Published Apr 24, 2017
·
Updated

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: AWT). Supported versions that are affected are Java SE: 7u131 and 8u121. 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 and while the vulnerability is in Java SE, attacks may significantly impact additional products. 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 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).

Affected Software

5 affected components
Oracle JDK=1.7.0-update131
Oracle JDK=1.8.0-update121
Oracle JRE=1.7.0-update_131
Oracle JRE=1.8.0-update_121
redhat Icedtea<3.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Oracle Java SE (AWT) to a version that resolves this vulnerability.

    Fixed in 7u131
  2. Upgrade

    Upgrade Oracle Java SE (AWT) to a version that resolves this vulnerability.

    Fixed in 8u121

Event History

Apr 24, 2017
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness
Data Sourced
via NVD·07:59 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-3512?

CVE-2017-3512 is considered a difficult to exploit vulnerability, but it can allow unauthenticated attackers to compromise affected versions of Java SE.

2

How do I fix CVE-2017-3512?

To fix CVE-2017-3512, upgrade to a supported version of Java SE that is not affected, specifically versions newer than 7u131 and 8u121.

3

Which versions of Java SE are affected by CVE-2017-3512?

CVE-2017-3512 affects Java SE versions 7u131 and 8u121, as well as their corresponding JRE versions.

4

Can CVE-2017-3512 be exploited remotely?

Yes, CVE-2017-3512 can be exploited by an unauthenticated attacker with network access via multiple protocols.

5

What components of Java SE are impacted by CVE-2017-3512?

CVE-2017-3512 impacts the AWT (Abstract Window Toolkit) component of Java SE.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203