Search for packages
| purl | pkg:deb/debian/kubernetes@0?distro=trixie |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-2ej9-nn86-7bet | Kubernetes kubectl cp Vulnerable to Symlink Attack The Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree. |
CVE-2019-11251
GHSA-6qfg-8799-r575 |
| VCID-57ar-astn-b7eu | 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. |
CVE-2019-11244
GHSA-2575-pghm-6qqx |
| VCID-6nk9-wkwg-ukeh | Information Exposure in Kubernetes Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name. |
CVE-2015-7528
GHSA-mqf3-28j7-3mj6 |
| VCID-cjth-qqvy-hqhk | Kubelet Incorrect Privilege Assignment In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit `runAsUser` attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified `mustRunAsNonRoot: true`, the kubelet will refuse to start the container as root. If the pod did not specify `mustRunAsNonRoot: true`, the kubelet will run the container as uid 0. |
CVE-2019-11245
GHSA-r76g-g87f-vw8f |
| VCID-dxej-zg13-63ff | Kubernetes did not effectively clear service account credentials In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig() |
CVE-2019-11243
GHSA-gc2p-g4fg-29vh |
| VCID-eztq-5cu5-7yfd | Kubernetes Arbitrary Command Injection In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection. ### Specific Go Packages Affected k8s.io/kubernetes/pkg/util/mount |
CVE-2018-1002101
GHSA-wqwf-x5cj-rg56 |
| VCID-fmcb-kpgu-5fcg | Authorization bypass in Openshift Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed. |
CVE-2016-1906
GHSA-m3fm-h5jp-q79p |
| VCID-humx-y4h8-pbeb | kubernetes: Incomplete fix for CVE-2019-1002101 allows for arbitrary file write via `kubectl cp` |
CVE-2019-11246
|
| VCID-k31a-cbd1-wkh5 | Access Restriction Bypass in kubernetes The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object. ### Specific Go Packages Affected github.com/kubernetes/kubernetes/pkg/apiserver |
CVE-2016-1905
GHSA-xx8c-m748-xr4j |
| VCID-m3n6-yj6t-y7eq | kubernetes: Incorrect default access permissions for Persistent Volumes |
CVE-2017-1002100
|
| VCID-qpg5-h1k8-yydt | Directory Traversal in Kubernetes Directory traversal vulnerability in Kubernetes, as used in Red Hat OpenShift Enterprise 3.0, allows attackers to write to arbitrary files via a crafted object type name, which is not properly handled before passing it to etcd. |
CVE-2015-5305
GHSA-jp32-vmm6-3vf5 |
| VCID-qxw4-2hry-uuf4 | Kubernetes Improper Input Validation vulnerability A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they are using an in-tree storage plugin for Windows nodes. |
CVE-2023-5528
GHSA-hq6q-c2x6-hmch |
| VCID-srhm-91w1-k3h7 | kubelet: runAsNonRoot logic bypass for Windows containers |
CVE-2021-25749
|
| VCID-sur2-ewj3-8bgx | Kubernetes allows Command Injection affecting Windows nodes via nodes/*/logs/query API A security vulnerability has been discovered in Kubernetes windows nodes that could allow a user with the ability to query a node's '/logs' endpoint to execute arbitrary commands on the host. This CVE affects only Windows worker nodes. Your worker node is vulnerable to this issue if it is running one of the affected versions listed below. |
CVE-2024-9042
GHSA-vv39-3w5q-974q |
| VCID-u8h6-kbws-8fbp | Sensitive Information leak via Log File in Kubernetes In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3. |
CVE-2020-8563
GHSA-5xfg-wv98-264m |
| VCID-vctf-a4t5-q7a2 | Unverified Ownership in Kubernetes Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect. |
CVE-2020-8554
GHSA-j9wf-vvm6-4r9w |
| VCID-vj7p-66bc-7yam | Symlink Attack in kubectl cp The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a tar inside the container, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. The untar function can both create and follow symbolic links. The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0. |
CVE-2019-1002101
GHSA-34jx-wx69-9x8v |
| VCID-w9b7-vajk-3kdq | Kube-proxy may unintentionally forward traffic Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (`spec.ports[*].port`) as a LoadBalancer Service when the LoadBalancer controller does not set the `status.loadBalancer.ingress[].ip` field. Clusters where the LoadBalancer controller sets the `status.loadBalancer.ingress[].ip` field are unaffected. |
CVE-2021-25736
GHSA-35c7-w35f-xwgh |
| VCID-xcss-tfeh-w7a6 | kubernetes: Incomplete fixes for CVE-2019-1002101 and CVE-2019-11246, kubectl cp potential directory traversal |
CVE-2019-11249
|
| VCID-zexe-7ywv-cbcf | Kubernetes sets incorrect permissions on Windows containers logs A security issue was discovered in Kubernetes clusters with Windows nodes where BUILTIN\Users may be able to read container logs and NT AUTHORITY\Authenticated Users may be able to modify container logs. |
CVE-2024-5321
GHSA-82m2-cv7p-4m75 |