An improper file permissions vulnerability affects Kata Containers prior to 1.11.5. When using a Kubernetes hostPath volume and mounting either a file or directory into a container as readonly, the file/directory is mounted as readOnly inside the container, but is still writable inside the guest. For a container breakout situation, a malicious guest can potentially modify or delete files/directories expected to be read-only.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Link | Tags |
---|---|
https://github.com/kata-containers/kata-containers/pull/1062 | third party advisory |
https://github.com/kata-containers/runtime/pull/3042 | third party advisory |
https://github.com/kata-containers/runtime/pull/3051 | third party advisory |
https://github.com/kata-containers/runtime/releases/tag/1.12.0 | third party advisory release notes |
https://github.com/kata-containers/runtime/releases/tag/1.11.5 | third party advisory release notes |