RHSA-2022:0444: Moderate: Red Hat Single Sign-On 7.4.10 on OpenJDK for OpenShift image security update
Red Hat Single Sign-On is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat Single Sign-On for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services.This erratum releases a new image for Red Hat Single Sign-On 7.4.10 for use within the OpenShift Container Platform 3.10, OpenShift Container Platform 3.11, and within the OpenShift Container Platform 4.3 cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release.Security Fix(es): log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender (CVE-2022-23305) log4j: Unsafe deserialization flaw in Chainsaw log viewer (CVE-2022-23307) log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender (CVE-2021-4104) log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink (CVE-2022-23302) 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:0444?
The severity of RHSA-2022:0444 is classified as Moderate.
How do I fix RHSA-2022:0444?
To fix RHSA-2022:0444, you should upgrade to the latest version of Red Hat Single Sign-On as recommended in the advisory.
What are the impacts of RHSA-2022:0444?
The impacts of RHSA-2022:0444 include potential vulnerability to unauthorized access or exploitation of authentication processes.
Which versions of Red Hat Single Sign-On are affected by RHSA-2022:0444?
RHSA-2022:0444 affects specific versions of Red Hat Single Sign-On as outlined in the advisory details.
Is there a workaround for RHSA-2022:0444?
There is no specific workaround for RHSA-2022:0444; patching is the recommended solution.