Technical impact
A flaw in CRI‑O allows a container using the optional Linux LinkLogs feature to create a symlink to a host log file even though the bind mount is intended to be read‑only. When conmon later appends log data, attacker‑controlled data is written to the host file, corrupting the integrity of audit logs. The vulnerability does not provide remote code execution; it is limited to tampering with host logs that conmon can write to.
Affected Systems
Red Hat OpenShift Container Platform versions 4 (specifically 4.15 and later) and 5, with CRI‑O running on the cluster nodes. The issue is present when the LinkLogs feature is enabled, which is not the default configuration.
Risk and Exploitability
The CVSS score of 6.4 indicates moderate severity. The EPSS value is unavailable, and the vulnerability is not listed in CISA’s KEV catalog. An attacker needs to run a non‑privileged container that can assume UID 0, have the LinkLogs feature enabled, and have an existing host log file that conmon can append to. The attack path is succinct: create a symlink in the pod to a future kubelet log path, then trigger conmon to write to the log, thereby inserting attacker data. While the exploit does not provide full control over the host, it compromises the integrity of audit and diagnostic logs, potentially hiding malicious activity and undermining forensic investigations.