Cri-o: malicious container can create symlink on host
- 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.30.1, 1.29.5, 1.28.7
- 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: no
- Technical impact: total
Summary
A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cri-o
From 1.30.0 · fixed in 1.30.1; From 1.29.4 · fixed in 1.29.5; From 1.28.6 · fixed in 1.28.7
- 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
- kernel
Version range not reported
- openshift
Version range not reported
- rhcos
Version range not reported
- container-tools:rhel8/podman
Version range not reported
- conmon
Version range not reported
- cri-o
Version range not reported
- github.com/cri-o/cri-oGo
From 1.28.6 · fixed in 1.28.7
- github.com/cri-o/cri-oGo
From 1.29.4 · fixed in 1.29.5
- github.com/cri-o/cri-oGo
From 1.30.0 · fixed in 1.30.1
- github.com/cri-o/cri-oGo
From 1.28.6 · fixed in 1.28.7; From 1.29.4 · fixed in 1.29.5; From 1.30.0 · fixed in 1.30.1