RHSA-2020:4350: Moderate: java-1.8.0-openjdk security and bug fix update
The java-1.8.0-openjdk packages provide the OpenJDK 8 Java Runtime Environment and the OpenJDK 8 Java Software Development Kit.Security Fix(es): OpenJDK: Credentials sent over unencrypted LDAP connection (JNDI, 8237990) (CVE-2020-14781) OpenJDK: Certificate blacklist bypass via alternate certificate encodings (Libraries, 8237995) (CVE-2020-14782) OpenJDK: Integer overflow leading to out-of-bounds access (Hotspot, 8241114) (CVE-2020-14792) OpenJDK: Incomplete check for invalid characters in URI to path conversion (Libraries, 8242685) (CVE-2020-14797) OpenJDK: Race condition in NIO Buffer boundary checks (Libraries, 8244136) (CVE-2020-14803) OpenJDK: High memory usage during deserialization of Proxy class with many interfaces (Serialization, 8236862) (CVE-2020-14779) OpenJDK: Missing permission check in path to URI conversion (Libraries, 8242680) (CVE-2020-14796) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Bug Fix(es): JDK-8215727: Restore JFR thread sampler loop to old / previous behavior (BZ#1889532)
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:4350?
RHSA-2020:4350 has been classified with a medium severity due to vulnerabilities related to unencrypted LDAP connections.
How do I fix RHSA-2020:4350?
To fix RHSA-2020:4350, upgrade to the latest recommended version of the OpenJDK packages as specified in the advisory.
What vulnerabilities are addressed in RHSA-2020:4350?
RHSA-2020:4350 addresses vulnerabilities including unencrypted LDAP credential transmission and certificate validation issues.
Which software versions are affected by RHSA-2020:4350?
RHSA-2020:4350 affects versions of the OpenJDK packages prior to 1.8.0-openjdk-1.8.0.272.b10-1.el7_9.
Is there a risk of data exposure with RHSA-2020:4350?
Yes, the vulnerabilities in RHSA-2020:4350 could potentially allow for credential exposure due to unencrypted LDAP connections.