RHSA-2020:2412: Moderate: OpenShift Container Platform 4.5 container image security update
Red Hat OpenShift Container Platform is Red Hat's cloud computingKubernetes application platform solution designed for on-premise or privatecloud deployments.Security Fix(es): golang.org/x/crypto: Processing of crafted ssh-ed25519 public keys allowed for panic (CVE-2020-9283) kubernetes: Denial of service in API server via crafted YAML payloads by authorized users (CVE-2019-11254) js-jquery: prototype pollution in object's prototype led to denial of service or remote code execution or property injection (CVE-2019-11358) kubernetes: node localhost services reachable via martian packets (CVE-2020-8558) containernetworking/plugins: IPv6 router advertisements allowed for MitM attacks on IPv4 clusters (CVE-2020-10749) jquery: Cross-site scripting due to improper injQuery.htmlPrefilter method (CVE-2020-11022) jQuery: passing HTML containing <option> elements to manipulation methods could result in untrusted code execution (CVE-2020-11023) 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-2020:2412?
The severity of RHSA-2020:2412 is categorized as important due to the potential for denial of service.
How do I fix RHSA-2020:2412?
To fix RHSA-2020:2412, update to the latest version of the Red Hat OpenShift Container Platform that addresses the vulnerabilities.
What vulnerabilities are addressed in RHSA-2020:2412?
RHSA-2020:2412 addresses vulnerabilities related to the processing of crafted ssh-ed25519 public keys in Golang's crypto library.
Does RHSA-2020:2412 affect all Red Hat OpenShift versions?
RHSA-2020:2412 specifically impacts certain versions of Red Hat OpenShift Container Platform, so users should check their version against the advisory.
Is there a workaround for RHSA-2020:2412?
There are no recommended workarounds for RHSA-2020:2412; updating to a secure version is the advised action.