medium
5.9
Advisory Published
CVE Published
Updated

CVE-2016-0695

First published: Mon Apr 18 2016(Updated: )

It was discovered that the Security component of OpenJDK failed to properly check DSA (Digital Signature Algorithm) parameters. The use of keys with incorrect parameters could lead to disclosure of sensitive data.

Credit: secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
Oracle JDK 6=1.6.0-update113
Oracle JDK 6=1.7.0-update99
Oracle JDK 6=1.8.0-update77
Oracle Java Runtime Environment (JRE)=1.6.0-update113
Oracle Java Runtime Environment (JRE)=1.7.0-update99
Oracle Java Runtime Environment (JRE)=1.8.0-update77
BEA JRockit=r28.3.9
Red Hat IcedTea 7<=2.6.6
Oracle Linux=5.0
Oracle Linux=6
Oracle Linux=7
redhat enterprise Linux desktop=5.0
redhat enterprise Linux desktop=6.0
redhat enterprise Linux desktop=7.0
Red Hat Enterprise Linux HPC Node=6.0
Red Hat Enterprise Linux HPC Node=7.0
Red Hat Enterprise Linux HPC Node=7.2
redhat enterprise Linux server=5.0
redhat enterprise Linux server=6.0
redhat enterprise Linux server=7.0
redhat enterprise Linux server aus=7.2
redhat enterprise Linux server eus=6.7.z
redhat enterprise Linux server eus=7.2
redhat enterprise Linux workstation=6.0
redhat enterprise Linux workstation=7.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-0695?

    CVE-2016-0695 is assessed as a high severity vulnerability due to potential disclosure of sensitive data.

  • How do I fix CVE-2016-0695?

    To fix CVE-2016-0695, update your Java SE to the latest version provided by Oracle that includes the security patch.

  • What systems are affected by CVE-2016-0695?

    CVE-2016-0695 affects Oracle JDK versions 1.6.0_update113, 1.7.0_update99, and 1.8.0_update77, as well as certain Oracle JRE versions.

  • What kind of attack can be executed through CVE-2016-0695?

    An attacker could potentially exploit CVE-2016-0695 to use keys with incorrect DSA parameters, leading to unauthorized access to sensitive data.

  • Is there a workaround for CVE-2016-0695?

    Currently, the only recommended solution for CVE-2016-0695 is to apply the updates from Oracle, as there are no effective workarounds.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203