CVE-2017-3259: Low severity Oracle JDK vulnerability

Published Jan 17, 2017
·
Updated

Oracle Java SE 6u141, 7u131, and 8u121 fixes an unspecified vulnerability in the Deployment component (CVE-2017-3259). Upstream has CVSS scored this issue as: 3.7/CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

External Reference:

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixJAVA

Other sources

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Deployment). Supported versions that are affected are Java SE: 6u131, 7u121 and 8u112. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE accessible data. 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 v3.0 Base Score 3.7 (Confidentiality impacts).

Affected Software

21 affected componentsFixes available
redhat/java<1.7.0-oracle-1:1.7.0.131-1jpp.1.el5_11
1.7.0-oracle-1:1.7.0.131-1jpp.1.el5_11
redhat/java<1.6.0-sun-1:1.6.0.141-1jpp.1.el5_11
1.6.0-sun-1:1.6.0.141-1jpp.1.el5_11
redhat/java<1.8.0-oracle-1:1.8.0.121-1jpp.1.el6_8
1.8.0-oracle-1:1.8.0.121-1jpp.1.el6_8
redhat/java<1.7.0-oracle-1:1.7.0.131-1jpp.1.el6_8
1.7.0-oracle-1:1.7.0.131-1jpp.1.el6_8
redhat/java<1.6.0-sun-1:1.6.0.141-1jpp.1.el6_8
1.6.0-sun-1:1.6.0.141-1jpp.1.el6_8
redhat/java<1.8.0-oracle-1:1.8.0.121-1jpp.1.el7_3
1.8.0-oracle-1:1.8.0.121-1jpp.1.el7_3
redhat/java<1.7.0-oracle-1:1.7.0.131-1jpp.1.el7_3
1.7.0-oracle-1:1.7.0.131-1jpp.1.el7_3
redhat/java<1.6.0-sun-1:1.6.0.141-1jpp.1.el7_3
1.6.0-sun-1:1.6.0.141-1jpp.1.el7_3
redhat/java<1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
redhat/java<1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
redhat/java<1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el6_8
1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el6_8
redhat/java<1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
redhat/java<1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
redhat/java<1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el7
1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el7
redhat/java<1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
Oracle JDK=1.6-update_131
Oracle JDK=1.7-update_121
Oracle JDK=1.8-update_112
ORACLE JRE=1.6-update_131
ORACLE JRE=1.7-update_121
ORACLE JRE=1.8-update_112

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.0-oracle-1:1.7.0.131-1jpp.1.el5_11
  2. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-sun-1:1.6.0.141-1jpp.1.el5_11
  3. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-oracle-1:1.8.0.121-1jpp.1.el6_8
  4. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.0-oracle-1:1.7.0.131-1jpp.1.el6_8
  5. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-sun-1:1.6.0.141-1jpp.1.el6_8
  6. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-oracle-1:1.8.0.121-1jpp.1.el7_3
  7. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.0-oracle-1:1.7.0.131-1jpp.1.el7_3
  8. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-sun-1:1.6.0.141-1jpp.1.el7_3
  9. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11
  10. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11
  11. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el6_8
  12. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8
  13. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_8
  14. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.8.0-ibm-1:1.8.0.4.0-1jpp.1.el7
  15. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el7
  16. Upgrade

    Upgrade Oracle Java SE Deployment to a version that resolves this vulnerability.

    Fixed in 6u141
  17. Upgrade

    Upgrade Oracle Java SE Deployment to a version that resolves this vulnerability.

    Fixed in 7u131
  18. Upgrade

    Upgrade Oracle Java SE Deployment to a version that resolves this vulnerability.

    Fixed in 8u121

Event History

Jan 17, 2017
CVE Published
12:00 AM
Data Sourced
via Red Hat·10:47 PM
DescriptionSeverityAffected Software
Jan 27, 2017
CVE Published
via MITRE·10:01 PM
Data Sourced
via MITRE·10:01 PM
DescriptionWeakness
Data Sourced
via NVD·10:59 PM
RemedyDescriptionSeverityAffected Software
Dec 11, 58332
Event
05:43 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-3259?

The CVSS score for CVE-2017-3259 is 3.7, indicating a low severity vulnerability.

2

How do I fix CVE-2017-3259?

You can mitigate CVE-2017-3259 by updating to the latest versions of affected Oracle Java packages listed in the remediation section.

3

Which versions of Oracle Java are affected by CVE-2017-3259?

CVE-2017-3259 affects Oracle Java SE 6u141, 7u131, and 8u121.

4

Is CVE-2017-3259 exploitable remotely?

Yes, CVE-2017-3259 has an attack vector of AV:N, meaning it can be exploited remotely.

5

Does CVE-2017-3259 impact system integrity?

CVE-2017-3259 has a low impact on confidentiality and does not affect integrity or availability.

Company

Resources

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