A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.
The product makes files or directories accessible to unauthorized actors, even though they should not be.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kubernetes | Kubernetes | * | 1.19.14 (including) |
| Kubernetes | Kubernetes | 1.20.0 (including) | 1.20.10 (including) |
| Kubernetes | Kubernetes | 1.21.0 (including) | 1.21.4 (including) |
| Kubernetes | Kubernetes | 1.22.0 (including) | 1.22.1 (including) |
| Red Hat OpenShift Container Platform 3.11 | RedHat | atomic-openshift-0:3.11.524-1.git.0.2dffce7.el7 | * |
| Red Hat OpenShift Container Platform 4.6 | RedHat | openshift-0:4.6.0-202109180038.p0.git.d5ed12c.assembly.stream.el8 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | openshift-0:4.7.0-202109172126.p0.git.bbbc079.assembly.stream.el7 | * |
| Red Hat OpenShift Container Platform 4.8 | RedHat | openshift-0:4.8.0-202109180335.p0.git.a620f50.assembly.stream.el7 | * |
Web servers, FTP servers, and similar servers may store a set of files underneath a “root” directory that is accessible to the server’s users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.