First published: Thu Apr 25 2019(Updated: )
In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. Upstream issue: <a href="https://github.com/kubernetes/kubernetes/issues/76676">https://github.com/kubernetes/kubernetes/issues/76676</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Kubernetes Dashboard | >=v1.8.0<v1.14.x |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1703209 is considered high due to the exposure of cached schema information with world-writeable permissions.
To fix REDHAT-BUG-1703209, ensure that the --cache-dir directory has restricted permissions and is not writable by unauthorized users.
Kubernetes versions v1.8.x to v1.14.x are affected by REDHAT-BUG-1703209.
The schema info cached by kubectl in the specified --cache-dir is impacted by REDHAT-BUG-1703209.
In multi-user environments, REDHAT-BUG-1703209 could lead to unauthorized access to sensitive configuration data stored in the cache.