Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket
Red Hat OpenShift Container Platform 4.16 · Red Hat OpenShift Container Platform 5
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat OpenShift Container Platform 4.16 | — |
|
| Red Hat Red Hat OpenShift Container Platform 5 | — | No fix yet |
Original description
A trust-boundary flaw in CRI-O's sandbox state persistence allows attacker-influenced pod metadata to overwrite CRI-O's own reserved sandbox bookkeeping; once reloaded as trusted after a restart, a later container recreate in that sandbox can expose a host-side runtime-management resource inside the container, enabling container escape.
From the CVE record · redhat