Advisory Published
Updated

REDHAT-BUG-1685717

First published: Tue Mar 05 2019(Updated: )

IBM JDK 8 SR5 FP30 (8.0.5.30) fixes a flaw described by upstream as: Eclipse OpenJ9 could allow a remote attacker to execute arbitrary code on the system, caused by the failure to omit a null check on the receiver object of an Unsafe call when accelerating it. An attacker could exploit this vulnerability to execute arbitrary code on the system. OpenJ9 upstream bug: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=544019">https://bugs.eclipse.org/bugs/show_bug.cgi?id=544019</a> Related OpenJ9 upstream commit seems to be: <a href="https://github.com/eclipse/openj9/commit/531d3f96fe9cdcf6baad9f6d6837be8fbc805d8d">https://github.com/eclipse/openj9/commit/531d3f96fe9cdcf6baad9f6d6837be8fbc805d8d</a> References: <a href="https://www-01.ibm.com/support/docview.wss?uid=ibm10873332">https://www-01.ibm.com/support/docview.wss?uid=ibm10873332</a> <a href="https://developer.ibm.com/javasdk/support/security-vulnerabilities/#IBM_Security_Update_March_2019">https://developer.ibm.com/javasdk/support/security-vulnerabilities/#IBM_Security_Update_March_2019</a>

Affected SoftwareAffected VersionHow to fix
IBM JDK 8
Eclipse OpenJ9

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.

Frequently Asked Questions

  • What is the severity of REDHAT-BUG-1685717?

    REDHAT-BUG-1685717 is classified as a high-severity vulnerability due to its potential to allow remote code execution.

  • How do I fix REDHAT-BUG-1685717?

    To fix REDHAT-BUG-1685717, you should update to IBM JDK 8 SR5 FP30 (8.0.5.30) or later versions that address this issue.

  • Who is affected by REDHAT-BUG-1685717?

    Users of IBM JDK 8 and Eclipse OpenJ9 who have not updated to the patched versions are affected by REDHAT-BUG-1685717.

  • What can happen if REDHAT-BUG-1685717 is exploited?

    If REDHAT-BUG-1685717 is exploited, a remote attacker could execute arbitrary code on the vulnerable system.

  • Is there a workaround for REDHAT-BUG-1685717?

    Currently, the recommended approach for REDHAT-BUG-1685717 is to apply the patch, as no official workaround is documented.

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