A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. This issue has its root in how runc handles Config Annotations lists.
CPE | Name | Operator | Version |
---|---|---|---|
github.com/opencontainers/runc | lt | 1.2.0-rc.1 |
access.redhat.com/security/cve/CVE-2024-3154
bugzilla.redhat.com/show_bug.cgi?id=2272532
github.com/cri-o/cri-o/security/advisories/GHSA-2cgq-h8xw-2v5j
github.com/opencontainers/runc
github.com/opencontainers/runc/commit/3db0871f1cf25c7025861ba0d51d25794cb21623
github.com/opencontainers/runc/pull/4217
github.com/opencontainers/runtime-spec/blob/main/features.md#unsafe-annotations-in-configjson
nvd.nist.gov/vuln/detail/CVE-2024-3154