Red Hat OpenShift Container Platform 4.12 vulnerabilities
96 known vulnerabilities in Red Hat OpenShift Container Platform 4.12 from Red Hat. 96 are rated high or critical, and 2 have been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.6 High severity
Red Hat OpenShift Container Platform 4.12: Incorrect Permission Assignment for Critical Resource
A flaw was found in the OpenShift build process, where the docker-build container is configured with a hostPath volume mount that maps the node's /var/lib/kubelet/config.json file into the build pod. This file contains sensitive credentials necessary for pulli
- 7.7 High severity
A flaw was found in kube-controller-manager.
A flaw was found in kube-controller-manager. This issue occurs when the initial application of a HPA config YAML lacking a .spec.behavior.scaleUp block causes a denial of service due to KCM pods going into restart churn.
- 8.2 High severity
Red Hat Enterprise Linux 8: Improper Link Resolution Before File Access
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the sys
- 9.1 Critical severity
Red Hat OpenShift Container Platform 4.12: Execution with Unnecessary Privileges
A flaw was found in openshift/builder. This vulnerability allows command injection via path traversal, where a malicious user can execute arbitrary commands on the OpenShift node running the builder container. When using the “Docker” strategy, executable files
- 9.9 Critical severity
Red Hat OpenShift Container Platform 4.12: Improper Privilege Management
A flaw was found in OpenShift. This issue occurs due to the misuse of elevated privileges in the OpenShift Container Platform's build process. During the build initialization step, the git-clone container is run with a privileged security context, allowing unr
- 8.0 High severity
Red Hat OpenShift Container Platform 4.12: Insufficient Entropy
An insufficient entropy vulnerability was found in the Openshift Console. In the authorization code type and implicit grant type, the OAuth2 protocol is vulnerable to a Cross-Site Request Forgery (CSRF) attack if the state parameter is used inefficiently. This
- 8.1 High severity
Red Hat OpenShift Container Platform 4.12: Improper Limitation of a Pathname to a Restricted Directory
A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system.
- 7.5 High severity
Red Hat OpenShift Container Platform 4.12: Authentication Bypass by Spoofing
A flaw was found in OpenShift's Telemeter. If certain conditions are in place, an attacker can use a forged token to bypass the issue ("iss") check during JSON web token (JWT) authentication.
- 7.2 High severity
Red Hat OpenShift Container Platform 4.12: Improper Neutralization of Special Elements used in a Command
A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
- 7.7 High severity
Red Hat OpenShift Container Platform 4.12: Exposure of Sensitive Information to an Unauthorized Actor
A credentials leak vulnerability was found in the cluster monitoring operator in OCP. This issue may allow a remote attacker who has basic login credentials to check the pod manifest to discover a repository pull secret.
- 7.5 High severity
Red Hat Ansible Automation Platform 2.4 for…: Missing Release of Memory after Effective Lifetime
A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects
- 8.6 High severity
Red Hat Enterprise Linux 8: Improper Link Resolution Before File Access
A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers. A malicious Containerfile can use a dummy image with a symbolic link to the root filesystem as a moun
- 8.6 High severity
runc: Exposure of Resource to Wrong Sphere
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a workin
- 7.2 High severity
Red Hat OpenShift Container Platform 4.11: Improper Privilege Management
A privilege escalation flaw was found in the node restriction admission plugin of the kubernetes api server of OpenShift. A remote attacker who modifies the node role label could steer workloads from the control plane and etcd nodes onto different worker nodes
- 7.8 High severity
Red Hat OpenShift Container Platform 4.11: Improper Control of Dynamically-Managed Code Resources
A vulnerability was found in cri-o. This issue allows the addition of arbitrary lines into /etc/passwd by use of a specially crafted environment variable.
- 8.0 High severity
Red Hat OpenShift Container Platform 4.10: Authentication Bypass Using an Alternate Path or Channel
An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote, authenticated attacker who has been given permissions "update, patch" the "pods/ephemeralcontainers" subresource beyond what the default is. They would th