Podman: The `podman run` command can be instructed to disable almost all sandboxing by image 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 5.8.8, 6.1.3
- 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
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Podman is a tool for managing OCI containers and pods. From 4.4.0 until 5.8.8 and 6.1.3, podman run treats an image carrying the io.podman.annotations.checkpoint.runtime.name annotation as a checkpoint and silently ignores user-supplied container creation restrictions such as --cap-drop=ALL, allowing image-controlled checkpoint state to select weaker sandbox settings and capabilities. Rootless containers are not affected because checkpoint and restore are unavailable in that mode. This issue is fixed in versions 5.8.8 and 6.1.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- podman-container-tools podman
From 4.4.0 · fixed in 5.8.8; From 6.0.0 · fixed in 6.1.3
- github.com/containers/podmanGo
From 4.4.0 · fixed in 5.8.8
- go.podman.io/podman/v6Go
From 6.0.0 · fixed in 6.1.3
- github.com/containers/podmanGo
All versions
- github.com/containers/podman/v2Go
All versions
- github.com/containers/podman/v3Go
All versions
- github.com/containers/podman/v4Go
From 4.4.0
- github.com/containers/podman/v5Go
fixed in 5.8.8