Kubernetes Unsafe Cacheing
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-11244US | medium5.0 | — | ||
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 permiss… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/108064WEB
- https://access.redhat.com/errata/RHSA-2019:3942WEB
- https://access.redhat.com/errata/RHSA-2020:0020WEB
- https://access.redhat.com/errata/RHSA-2020:0074WEB
- https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7dWEB
- https://github.com/kubernetes/kubernetes/issues/76676WEB
- https://github.com/kubernetes/kubernetes/pull/77874WEB
- https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan