RHSA-2022:1437: Important: OpenJDK 17.0.3 security update for Windows Builds
The OpenJDK 17 packages provide the OpenJDK 17 Java Runtime Environment and the OpenJDK 17 Java Software Development Kit.This release of the Red Hat build of OpenJDK 17 (17.0.3) for portable Linuxserves as a replacement for the Red Hat build of OpenJDK 17 (17.0.2) andincludes security and bug fixes, and enhancements. For further information,refer to the release notes linked to in the References section.Security Fix(es): OpenJDK: Unbounded memory allocation when compiling crafted XPath expressions (JAXP, 8270504) (CVE-2022-21426) OpenJDK: Missing check for negative ObjectIdentifier (Libraries, 8275151) (CVE-2022-21443) OpenJDK: Improper object-to-string conversion in AnnotationInvocationHandler (Libraries, 8277672) (CVE-2022-21434) OpenJDK: Defective secure validation in Apache Santuario (Libraries, 8278008) (CVE-2022-21476) OpenJDK: URI parsing inconsistencies (JNDI, 8278972) (CVE-2022-21496) OpenJDK: Improper ECDSA signature verification (Libraries, 8277233) (CVE-2022-21449) 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2022:1437?
The severity of RHSA-2022:1437 is classified as important.
How do I fix RHSA-2022:1437?
To fix RHSA-2022:1437, update to the latest version of OpenJDK 17 available in your repository.
What versions are affected by RHSA-2022:1437?
RHSA-2022:1437 affects the Red Hat build of OpenJDK 17 prior to version 17.0.3.
What are the main vulnerabilities addressed in RHSA-2022:1437?
RHSA-2022:1437 addresses multiple vulnerabilities related to security issues in OpenJDK 17.
Is it necessary to restart my application after applying RHSA-2022:1437?
Yes, it is generally necessary to restart your application to apply the updates from RHSA-2022:1437.