Database/Container, Kubernetes & orchestration
CRI-O: Shipped OpenShift CRI-O builds regressed the CVE-2022-2995 fix
CVSS 4.8CVE-2022-3466Container, Kubernetes & orchestrationcurated
Impact
Shipped OpenShift CRI-O builds regressed the CVE-2022-2995 fix; supply-chain style reintroduction of a fixed bug
Who can reach it
Any tenant workload on an affected OCP build
What to do
Verify CRI-O build version explicitly, not just the OCP version; upgrade and drain
References
Related entries
- CRI-O: "Safe" sysctls applied to the host when a pod uses host IPC/networkCVE-2022-0532 · CRI-OMedium
- CRI-O: Ambient-capability mishandling runs containers with elevated privilegesCVE-2018-1000400 · CRI-OHigh
- CRI-O: "cr8escape": kernel sysctl injection via pod spec gives container escape and arbitrary code executionCVE-2022-0811 · CRI-OHigh
- CRI-O: Malicious container creates a symlink via directory traversal and gets arbitrary host read/writeCVE-2024-5154 · CRI-OHigh
- CRI-O: Crafted environment variable injects arbitrary lines into /etc/passwdCVE-2022-4318 · CRI-OHigh
- CRI-O: Unbounded ExecSync output exhausts node memory or diskCVE-2022-1708 · CRI-OHigh
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.