CVE-2024-3154: CRI-O Arbitrary Systemd Property Injection
Summary
CVE-2024-3154: CRI-O vulnerable to an arbitrary systemd property injection. Affects github.com/cri-o/cri-o across 3 version ranges.
< 1.27.6
>= 1.28.0, < 1.28.6
>= 1.29.0, < 1.29.4
Fixed in 1.27.6, 1.28.6 or 1.29.4, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
CRI-O is an open-source container runtime for Kubernetes that allows users to run containers directly from Kubernetes. It is written in Go and provides a lightweight alternative to traditional container runtimes. CRI-O is widely used in production environments and offers features such as image management, container lifecycle management, and resource isolation. However, a vulnerability has been discovered in CRI-O that allows for arbitrary systemd property injection.
Vulnerability Detail
The vulnerability in CRI-O allows an attacker to inject an arbitrary systemd property via a Pod annotation. By creating a Pod with a specific annotation, an attacker can execute arbitrary actions on the host system. This can lead to unauthorized access, privilege escalation, and potential disruption of the host system. The vulnerability affects CRI-O versions 0 to 1.29.3, 1.28.0 to 1.28.5, and 1.27.0 to 1.27.5.
How To Fix
Latest published version: v1.37.2 as of 23 Oct 2026
go get github.com/cri-o/cri-o@v1.37.2Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.27.61.27.6go get github.com/cri-o/cri-o@v1.27.6 -
>= 1.28.0, < 1.28.61.28.6go get github.com/cri-o/cri-o@v1.28.6 -
>= 1.29.0, < 1.29.41.29.4go get github.com/cri-o/cri-o@v1.29.4
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
Unfortunately, there are no known workarounds for this vulnerability. The only effective solution is to update CRI-O to the fixed versions mentioned above.
Conclusion
The vulnerability in CRI-O that allows for arbitrary systemd property injection poses a significant risk to users. It is crucial to update CRI-O to the fixed versions mentioned above to mitigate the risk of exploitation. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/cri-o/cri-o →
FAQ
CRI-O is an open-source container runtime for Kubernetes that provides a lightweight alternative to traditional container runtimes.
The vulnerability allows an attacker to inject arbitrary systemd properties via Pod annotations, potentially leading to unauthorized access and disruption of the host system.
CRI-O versions 0 to 1.29.3, 1.28.0 to 1.28.5, and 1.27.0 to 1.27.5 are affected by this vulnerability.
No, there are no known workarounds for this vulnerability. Updating to the fixed versions is the recommended solution.
To update CRI-O, follow the official documentation provided by the CRI-O project. It is recommended to update to version 1.29.4, 1.28.6, or 1.27.6, depending on the affected version.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/cri-o/cri-o.
