On CRI-O, it looks like an arbitrary systemd property can be injected via a Pod annotation. This means that any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. References: https://github.com/opencontainers/runc/pull/3923#discussion_r1538109353 https://github.com/cri-o/cri-o/security/advisories/GHSA-2cgq-h8xw-2v5j
Created cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278702] Created cri-o:1.21/cri-o tracking bugs for this issue: Affects: epel-all [bug 2278701] Created cri-o:1.22/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278703] Created cri-o:1.23/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278704] Created cri-o:1.24/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278705] Created cri-o:1.25/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278706] Created cri-o:1.26/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278707] Created cri-o:1.27/cri-o tracking bugs for this issue: Affects: fedora-all [bug 2278708]
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2024:2669 https://access.redhat.com/errata/RHSA-2024:2669
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2024:2672 https://access.redhat.com/errata/RHSA-2024:2672
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2024:2784 https://access.redhat.com/errata/RHSA-2024:2784
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2024:3496 https://access.redhat.com/errata/RHSA-2024:3496