Most severe vulnerabilities for "red hat openshift container platform" 4.5

Where

AND

Sort:

redhat/github.com/openshift/builder v0.0.0-20210118193943A privilege escalation vulnerability exists in the build functionality of OpenShift Container Platfo…

Risk 81

Severity

8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

A privilege escalation flaw was found in openshift4/ose-docker-builder. The build container runs with high privileges using a chrooted environment instead of runc. If an attacker can gain access to this build container, they can potentially utilize the raw devices of the underlying node, such as the network and storage devices, to at least escalate their privileges to that of the cluster admin. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

1 / 2

Remedy

The affected build strategies include docker, source and custom builds, hence these can be disabled as per the documentation[1]. This does however, exclude the Jenkins build strategy as it is not affected and does not have to be disabled. [1] https://docs.openshift.com/container-platform/4.6/builds/securing-builds-by-strategy.html On clusters where builds are allowed only grant permissions to perform builds to users who you wish to be to able to view, modify and edit all cluster resources.

First published (updated )

CVE-2021-20182

redhat/kernelUse After Free

Risk 69

Severity

7.8

Use After Free

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

A flaw was found in the Linux kernel’s implementation of MIDI, where an attacker with a local account and the permissions to issue ioctl commands to midi devices could trigger a use-after-free issue. A write to this specific memory while freed and before use causes the flow of execution to change and possibly allow for memory corruption or privilege escalation. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

1 / 2

Source: MITRE

First published (updated )

CVE-2020-27786

Linux Linux kernelInput Validation

Risk 72

Severity

7.8

Input Validation

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Last updated 25 April 2025

1 / 3

Source: Ubuntu

First published (updated )

CVE-2021-20194

redhat/kernelLast updated 25 April 2025

Risk 67

Severity

7.2

AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

A flaw was found in the way RTAS handled memory accesses in userspace to kernel communication. On a locked down (usually due to Secure Boot) guest system running on top of PowerVM or KVM hypervisors (pseries platform) a root like local user could use this flaw to further increase their privileges to that of a running kernel.

1 / 5

Remedy

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

First published (updated )

CVE-2020-27777