Cri-o: cri-o: unvalidated image env var causes daemon crash
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.34.11, 1.35.7 and 1.36.3.
A flaw was found in CRI-O's container-creation environment-variable handling (`mergeEnvs` in `server/utils.go`, consumed by `setupContainerEnvironmentAndWorkdir` in `server/container_create.go`). When a `CreateContainer` request supplies a `nil` CRI `Envs` field, CRI-O falls back to using the target OCI image's `config.Env` entries unfiltered, in contrast to the normal merge path, which validates each entry for a `key=value` form before use. An OCI image whose `config.Env` contains an entry with no `=` character (e.g. a bare `NOEQUALS` string) causes CRI-O to split that entry into a single-element slice and then index its second element, which is out of range. This triggers an unrecovered Go runtime panic in the `crio` daemon process, crashing it and terminating the container-runtime service for all workloads on the node until it is restarted.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Red Hat | OpenShift Container Platform | ||
| <1.34.11, <1.35.7, <1.36.3 | 1.34.11, 1.35.7, 1.36.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Red Hat, strongest first
Embed
A live severity badge for an advisory, README or ticket