CyberRota Analysis
AI-GeneratedThe crun container runtime prior to version 1.28 is vulnerable due to its default device setup, which improperly handles symlinks in the `/dev` directory, potentially leading to the creation of device nodes and symlinks outside the intended container root filesystem. This flaw can result in unauthorized access and manipulation of system resources, particularly in environments where containers are run with elevated privileges. Organizations using crun for container management should prioritize upgrading to version 1.28 to mitigate the risk of local privilege escalation and unintended system modifications.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
crun is an open source OCI Container Runtime fully written in C. Prior to version 1.28, crun's default device setup opens the container rootfs `/dev` directory without `O_NOFOLLOW`. If an OCI bundle contains `rootfs/dev` as a symlink and the bundle configuration does not mount `/dev`, crun follows that symlink and creates the default device nodes and stdio symlinks at the symlink target outside the container rootfs. In a local rootful crun replay, this created fixed device nodes and symlinks outside the rootfs before crun returned failure. A pre-existing file named `ptmx` in the target directory was also replaced by crun's forced `ptmx -> pts/ptmx` symlink. Version 1.28 fixes the issue.