CVE-2024-3154GHSA-2CGQ-H8XW-2V5JGO-2024-2791
Cri-o: arbitrary command injection via pod annotation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.29.4, 1.28.6, 1.27.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cri-o
1.27.5, 1.28.5, 1.29.3
- cri-o
Version range not reported
- cri-o
Version range not reported
- cri-o
Version range not reported
- cri-o
Version range not reported
- cri-o
Version range not reported
- github.com/cri-o/cri-oGo
From 1.29.0 · fixed in 1.29.4
- github.com/cri-o/cri-oGo
From 1.28.0 · fixed in 1.28.6
- github.com/cri-o/cri-oGo
fixed in 1.27.6
- github.com/cri-o/cri-oGo
fixed in 1.27.6; From 1.28.0 · fixed in 1.28.6; From 1.29.0 · fixed in 1.29.4