Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | Confidential Compute Attestation | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 5 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 5 | unaffected | — |
| Red Hat | Red Hat OpenShift Container Platform 5 | affected | — |
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Cri-o | Cri-o |
|
||||||||
| Cri-o | Cri-o |
|
||||||||
| Redhat | Openshift Container Platform |
|
||||||||
| Redhat | Openshift Container Platform |
|
Vendor Workaround
Red Hat OpenShift's default restricted / restricted-v2 SCCs do not allow containers to run as UID 0. That blocks the tested attack, even though LinkLogs is allowed in CRI-O on 4.15 and later.SELinux is enforcing on OpenShift nodes and further limits which host files conmon can write. Do not disable SELinux. Until a fixed cri-o build is installed, customers should: 1. Keep default SCCs. Do not grant anyuid, privileged, or other SCCs that allow host UID 0 to untrusted projects. 2. Review existing grants. Find namespaces/SAs that can run as UID 0.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.216% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cri-o
Cri-o cri-o Redhat openshift Container Platform |
|
| Vendors & Products |
Cri-o
Cri-o cri-o Redhat openshift Container Platform |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat confidential Compute Attestation
|
|
| CPEs | cpe:/a:redhat:confidential_compute_attestation:1 | |
| Vendors & Products |
Redhat confidential Compute Attestation
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MS_RDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can place a symlink at a future kubelet log path so that privileged conmon later appends attacker-controlled log data to an existing host file. This is an append-only host integrity issue, not universal remote code execution; LinkLogs is not enabled by default. | |
| Title | Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes | |
| First Time appeared |
Redhat
Redhat openshift |
|
| Weaknesses | CWE-59 | |
| CPEs | cpe:/a:redhat:openshift:4 cpe:/a:redhat:openshift:5 |
|
| Vendors & Products |
Redhat
Redhat openshift |
|
| References |
| |
| Metrics |
cvssV3_1
|