# CVE-2024-3154: GO-2024-2791 - CRI-O vulnerable to an arbitrary systemd property injection in github.com/cri-o/cri-o

Source: https://junglewise.ai/threats/cve-2024-3154-cri-o-vulnerable-to-an-arbitrary-systemd-property-injection  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-06-04  
License: CC BY 4.0 with a link back

CVE-2024-3154 · Severity: low · CVSS 3.1 · Published 2024-06-04

CRI-O vulnerable to an arbitrary systemd property injection in github.com/cri-o/cri-o

Technologies: [github.com/cri-o/cri-o (Go)](https://junglewise.ai/threats/technologies/github-com-cri-o-cri-o). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2024-3154 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-3154 being exploited in the wild.

**How severe is CVE-2024-3154?** Low severity, with a CVSS score of 3.1, published 4 June 2024.

**Which products and versions are affected?** github.com/cri-o/cri-o (Go) SEMVER:introduced=0,fixed=1.27.6,introduced=1.28.0,fixed=1.28.6,introduced=1.29.0,fixed=1.29.4, SEMVER:introduced=1.29.0,fixed=1.29.4.

**Is there a fix for CVE-2024-3154?** Yes. github.com/cri-o/cri-o (Go): upgrade to 1.29.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-3154?** Check whether you run github.com/cri-o/cri-o (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/cri-o/cri-o (Go): upgrade to 1.29.4 or later

  ```sh
  go get github.com/cri-o/cri-o@v1.29.4
  ```


## Affected products

- github.com/cri-o/cri-o (Go) SEMVER:introduced=0,fixed=1.27.6,introduced=1.28.0,fixed=1.28.6,introduced=1.29.0,fixed=1.29.4, SEMVER:introduced=1.29.0,fixed=1.29.4

## Identifiers

- CVE-2024-3154
- GHSA-2cgq-h8xw-2v5j
- GO-2024-2791

## Related threats

- [GO-2025-3897 - CRI-O has Potential High Memory Consumption from File Read in github.com/cri-o/cri-o](https://junglewise.ai/threats/cve-2025-4437-cri-o-has-potential-high-memory-consumption-from-file-read)
- [GO-2025-3426 - CRI-O Path Traversal vulnerability in github.com/cri-o/cri-o](https://junglewise.ai/threats/cve-2025-0750-cri-o-path-traversal-vulnerability)
- [GO-2024-3292 - CRI-O: Maliciously structured checkpoint file can gain arbitrary node access in github.com/cri-o/cri-o](https://junglewise.ai/threats/cve-2024-8676-cri-o-maliciously-structured-checkpoint-file-can-gain-arbitrary)
- [GO-2022-1206 - CRI-O vulnerable to /etc/passwd tampering resulting in Privilege Escalation in github.com/cri-o/cri-o](https://junglewise.ai/threats/cve-2022-4318-cri-o-vulnerable-to-etc-passwd-tampering-resulting-in-privilege)
- [CRI-O incorrect handling of supplementary groups may lead to sensitive information disclosure](https://junglewise.ai/threats/cve-2022-2995-cri-o-incorrect-handling-of-supplementary-groups-may-lead-to)