REDHAT-BUG-2015648: Medium severity OpenJDK JSSE vulnerability

Published Oct 19, 2021
·
Updated

It was discovered that the default TLS cipher suite configuration in the JSSE component of OpenJDK preferred certain weak ciphers over stronger ciphers. This issue was addressed by:

- Preferring ciphers with forward secrecy. - Lowering priority of ciphers using RSA encryption key exchange. - Lowering priority of ciphers using SHA-1 hashing algorithm.

Upstream commit:

https://github.com/openjdk/jdk11u/commit/af4b37301d33723806c38cf8ae5d85b7fa7ef39f

Affected Software

1 affected component
OpenJDK JSSE

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch af4b37301d33723806c38cf8ae5d85b7fa7ef39f
  2. Configuration

    Update the JSSE default TLS cipher suite configuration so that ciphers offering forward secrecy are preferred, and ciphers using RSA key exchange or the SHA-1 hashing algorithm have lower priority. Deploy the updated configuration to all affected OpenJDK JSSE instances.

    Sun JSSE (OpenJDK JSSE default TLS cipher suite configuration) default TLS cipher suite ordering = prefer ciphers with forward secrecy; lower priority for RSA key-exchange ciphers; lower priority for ciphers using SHA-1
  3. Compensating control

    If you cannot apply the JSSE configuration change or upstream commit immediately, enforce cipher-suite ordering at TLS termination (for example on load balancers, reverse proxies, or TLS terminators) to prefer forward-secrecy ciphers and de-prioritize or disable RSA key-exchange and SHA-1-based ciphers.

Event History

Oct 19, 2021
Data Sourced
via Red Hat·06:35 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2015648?

The severity of REDHAT-BUG-2015648 is significant due to the preference for weak TLS ciphers which can lead to potential security vulnerabilities.

2

How do I fix REDHAT-BUG-2015648?

To fix REDHAT-BUG-2015648, update your OpenJDK JSSE to the latest version where the cipher suite configuration is corrected.

3

What are the risks associated with REDHAT-BUG-2015648?

The risks associated with REDHAT-BUG-2015648 include data interception and denial of service due to the use of weak TLS ciphers.

4

Which versions of OpenJDK are affected by REDHAT-BUG-2015648?

OpenJDK JSSE versions prior to the patch addressing REDHAT-BUG-2015648 are affected.

5

What changes were made to resolve REDHAT-BUG-2015648?

The changes made to resolve REDHAT-BUG-2015648 include preferring ciphers with forward secrecy and lowering the priority of ciphers using RSA encryption.

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