Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update golangci/golangci-lint-action action to v6 #16

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update golangci/golangci-lint-action action to v6 #16

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 8, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
golangci/golangci-lint-action action major v3.7.0 -> v6.5.0

Release Notes

golangci/golangci-lint-action (golangci/golangci-lint-action)

v6.5.0

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v6.4.1...v6.5.0

v6.4.1

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v6.4.0...v6.4.1

v6.4.0

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v6.3.3...v6.4.0

v6.3.3

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v6.3.2...v6.3.3

v6.3.2

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v6.3.1...v6.3.2

v6.3.1

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v6.3.0...v6.3.1

v6.3.0

Compare Source

What's Changed

Changes
Documentation
Dependencies

New Contributors

Full Changelog: golangci/golangci-lint-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

What's Changed

Changes
Documentation
Dependencies

New Contributors

Full Changelog: golangci/golangci-lint-action@v6.1.1...v6.2.0

v6.1.1

Compare Source

What's Changed
Changes
Documentation
Dependencies
New Contributors

Full Changelog: golangci/golangci-lint-action@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

Changes
Documentation
Dependencies

Full Changelog: golangci/golangci-lint-action@v6.0.1...v6.1.0

v6.0.1

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

What's Changed

This version removes annotations option (because it was useless), and removes the default output format (github-actions).
The annotations are still produced but with another approach.

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v5.3.0...v6.0.0

v5.3.0

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v5.2.0...v5.3.0

v5.2.0

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v5.0.0...v5.1.0

v5.0.0

Compare Source

What's Changed

skip-pkg-cache and skip-build-cache have been removed because the cache related to Go itself is already handled by actions/setup-go.

Changes

New Contributors

Full Changelog: golangci/golangci-lint-action@v4.0.1...v5.0.0

v4.0.1

Compare Source

What's Changed

Documentation
Dependencies

New Contributors

Full Changelog: golangci/golangci-lint-action@v4.0.0...v4.0.1

v4.0.0

Compare Source

What's Changed

In the scope of this release, we change Nodejs runtime from node16 to node20 (https://github.com/golangci/golangci-lint-action/pull/843).

Documentation
Dependencies

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from ab431ba to 821f213 Compare July 30, 2024 02:22
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from 821f213 to d73499e Compare October 5, 2024 02:48
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from d73499e to 364c007 Compare January 17, 2025 07:49
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from 364c007 to 6309984 Compare February 6, 2025 08:09
@qodo-merge-pro-for-open-source Qodo Merge Pro for Open Source
Copy link

qodo-merge-pro-for-open-source bot commented Feb 6, 2025 •
edited
Loading

CI Feedback 🧐

(Feedback updated until commit 24ab354)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Test

Failed stage: Test [❌]

Failed test name: Test_ParseVulneDB

Failure summary:

The test 'Test_ParseVulneDB' failed because there was a mismatch between the expected and actual
output. The test was comparing two JSON strings containing vulnerability data, and they did not
match. The error message shows that the actual output had different content than what was expected.

Relevant error logs: 
1:  ##[group]Operating System
2:  Ubuntu
...

53:  Adding to the cache ...
54:  Successfully cached go to /opt/hostedtoolcache/go/1.18.10/x64
55:  Added go to the path
56:  Successfully set up Go version 1.18
57:  [command]/opt/hostedtoolcache/go/1.18.10/x64/bin/go env GOMODCACHE
58:  [command]/opt/hostedtoolcache/go/1.18.10/x64/bin/go env GOCACHE
59:  /home/runner/go/pkg/mod
60:  /home/runner/.cache/go-build
61:  ##[warning]Restore cache failed: Dependencies file is not found in /home/runner/work/k8s-db-collector/k8s-db-collector. Supported file pattern: go.sum
...

222:  �[36;1mgo test -v ./...�[0m
223:  shell: /usr/bin/bash -e {0}
224:  ##[endgroup]
225:  ?   	github.com/khulnasoft-lab/k8s-db-collector	[no test files]
226:  ?   	github.com/khulnasoft-lab/k8s-db-collector/collectors	[no test files]
227:  ?   	github.com/khulnasoft-lab/k8s-db-collector/collectors/cvedb	[no test files]
228:  === RUN   Test_ParseVulneDB
229:  collector_test.go:25: 
230:  Error Trace:	/home/runner/work/k8s-db-collector/k8s-db-collector/collectors/cvedb/cve/collector_test.go:25
231:  Error:      	Not equal: 
232:  expected: "[{\"id\":\"CVE-2023-2431\",\"created_at\":\"2023-06-15T14:42:32Z\",\"summary\":\"Bypass of seccomp profile enforcement \",\"component\":\"k8s.io/kubelet\",\"details\":\"A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"fixed\":\"1.25.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"fixed\":\"1.26.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"fixed\":\"1.27.1\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118690\",\"https://www.cve.org/cverecord?id=CVE-2023-2431\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N\",\"Score\":3.4},\"severity\":\"Low\"},{\"id\":\"CVE-2023-2727\",\"created_at\":\"2023-06-13T14:42:06Z\",\"summary\":\"Bypassing policies imposed by the ImagePolicyWebhook and bypassing mountable secrets policy imposed by the ServiceAccount admission plugin\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may be able to launch containers using images that are restricted by ImagePolicyWebhook when using ephemeral containers. Kubernetes clusters are only affected if the ImagePolicyWebhook admission plugin is used together with ephemeral containers.\\n\\n\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"last_affected\":\"1.26.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"last_affected\":\"1.27.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118640\",\"https://www.cve.org/cverecord?id=CVE-2023-2727, CVE-2023-2728\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2023-2728\",\"created_at\":\"2023-06-13T14:42:06Z\",\"summary\":\"Bypassing policies imposed by the ImagePolicyWebhook and bypassing mountable secrets policy imposed by the ServiceAccount admission plugin\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.\\n\\n\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"last_affected\":\"1.26.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"last_affected\":\"1.27.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118640\",\"https://www.cve.org/cverecord?id=CVE-2023-2727, CVE-2023-2728\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2023-2878\",\"created_at\":\"2023-06-02T19:03:54Z\",\"summary\":\"secrets-store-csi-driver discloses service account tokens in logs\",\"component\":\"sigs.k8s.io/secrets-store-csi-driver\",\"details\":\"Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.\\n\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.3.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118419\",\"https://www.cve.org/cverecord?id=CVE-2023-2878\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2022-3294\",\"created_at\":\"2022-11-08T21:33:26Z\",\"summary\":\"Node address isn't always verified when proxying\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"last_affected\":\"1.23.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.15\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/113757\",\"https://www.cve.org/cverecord?id=CVE-2022-3294\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H\",\"Score\":6.6},\"severity\":\"Medium\"},{\"id\":\"CVE-2022-3162\",\"created_at\":\"2022-11-08T21:33:07Z\",\"summary\":\"Unauthorized read of Custom Resources\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"last_affected\":\"1.23.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.15\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/113756\",\"https://www.cve.org/cverecord?id=CVE-2022-3162\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2021-25749\",\"created_at\":\"2022-09-01T21:02:01Z\",\"summary\":\"`runAsNonRoot` logic bypass for Windows containers\",\"component\":\"k8s.io/kubelet\",\"details\":\"Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"fixed\":\"1.22.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"fixed\":\"1.23.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"fixed\":\"1.24.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/112192\",\"https://www.cve.org/cverecord?id=CVE-2021-25749\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"Score\":7.8},\"severity\":\"High\"},{\"id\":\"CVE-2021-25741\",\"created_at\":\"2021-09-13T20:58:56Z\",\"summary\":\"Symlink Exchange Can Allow Host Filesystem Access\",\"component\":\"k8s.io/kubelet\",\"details\":\"A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files \\u0026 directories outside of the volume, including on the host filesystem.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.21.0\"},{\"last_affected\":\"1.21.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.1\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/104980\",\"https://www.cve.org/cverecord?id=CVE-2021-25741\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"Score\":8.8},\"severity\":\"High\"},{\"id\":\"CVE-2021-25737\",\"created_at\":\"2021-05-18T19:14:27Z\",\"summary\":\"Holes in EndpointSlice Validation Enable Host Network Hijack\",\"component\":\"k8s.io/apiserver\",\"details\":\"A security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.18\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.6\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.21.0\"},{\"last_affected\":\"1.21.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/102106\",\"https://www.cve.org/cverecord?id=CVE-2021-25737\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N\",\"Score\":2.7},\"severity\":\"Low\"},{\"id\":\"CVE-2021-25735\",\"created_at\":\"2021-03-10T18:18:01Z\",\"summary\":\"Validating Admission Webhook does not observe some previous fields\",\"component\":\"k8s.io/apiserver\",\"details\":\"A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. Clusters are only affected by this vulnerability if they run a Validating Admission Webhook for Nodes that denies admission based at least partially on the old state of the Node object. Validating Admission Webhook does not observe some previous fields.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.17\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/100096\",\"https://www.cve.org/cverecord?id=CVE-2021-25735\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8566\",\"created_at\":\"2020-10-15T22:07:53Z\",\"summary\":\"Ceph RBD adminSecrets exposed in logs when loglevel \\u003e= 4\",\"component\":\"k8s.io/controller-manager\",\"details\":\"In Kubernetes clusters using Ceph RBD as a storage provisioner, with logging level of at least 4, Ceph RBD admin secrets can be written to logs. This occurs in kube-controller-manager's logs during provisioning of Ceph RBD persistent claims. This affects \\u003c v1.19.3, \\u003c v1.18.10, \\u003c v1.17.13.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.13\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95624\",\"https://www.cve.org/cverecord?id=CVE-2020-8566\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8565\",\"created_at\":\"2020-10-15T22:05:32Z\",\"summary\":\"Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel \\u003e= 9\",\"component\":\"k8s.io/kubectl\",\"details\":\"In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects \\u003c= v1.19.3, \\u003c= v1.18.10, \\u003c= v1.17.13, \\u003c v1.20.0-alpha2.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"last_affected\":\"1.17.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"fixed\":\"1.20.0-alpha2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95623\",\"https://www.cve.org/cverecord?id=CVE-2020-8565\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8564\",\"created_at\":\"2020-10-15T22:03:19Z\",\"summary\":\"Docker config secrets leaked when file is malformed and log level \\u003e= 4\",\"component\":\"k8s.io/kubernetes\",\"details\":\"In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects \\u003c v1.19.3, \\u003c v1.18.10, \\u003c v1.17.13.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.13\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95622\",\"https://www.cve.org/cverecord?id=CVE-2020-8564\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8563\",\"created_at\":\"2020-10-15T22:00:44Z\",\"summary\":\"Secret leaks in kube-controller-manager when using vSphere provider\",\"component\":\"k8s.io/controller-manager\",\"details\":\"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 \\u003c v1.19.3.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95621\",\"https://www.cve.org/cverecord?id=CVE-2020-8563\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8557\",\"created_at\":\"2020-07-13T18:39:08Z\",\"summary\":\"Node disk DOS by writing to container /etc/hosts\",\"component\":\"k8s.io/kubelet\",\"details\":\"The Kubernetes kubelet component in versions 1.1-1.16.12, 1.17.0-1.17.8 and 1.18.0-1.18.5 do not account for disk usage by a pod which writes to its own /etc/hosts file. The /etc/hosts file mounted in a pod by kubelet is not included by the kubelet eviction manager when calculating ephemeral storage usage by a pod. If a pod writes a large amount of data to the /etc/hosts file, it could fill the storage space of the node and cause the node to fail.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.16.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.6\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/93032\",\"https://www.cve.org/cverecord?id=CVE-2020-8557\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"Score\":5.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8559\",\"created_at\":\"2020-07-08T17:03:16Z\",\"summary\":\"Privilege escalation from compromised node to cluster\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes kube-apiserver in versions v1.6-v1.15, and versions prior to v1.16.13, v1.17.9 and v1.18.6 are vulnerable to an unvalidated redirect on proxied upgrade requests that could allow an attacker to escalate privileges from a node compromise to a full cluster compromise.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.6.0\"},{\"last_affected\":\"1.16.12\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"last_affected\":\"1.17.8\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/92914\",\"https://www.cve.org/cverecord?id=CVE-2020-8559\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H\",\"Score\":6.4},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8558\",\"created_at\":\"2020-06-19T18:38:58Z\",\"summary\":\"Node setting allows for neighboring hosts to bypass localhost boundary\",\"component\":\"k8s.io/kubelet\",\"details\":\"The Kubelet and kube-proxy components in versions 1.1.0-1.16.10, 1.17.0-1.17.6, and 1.18.0-1.18.3 were found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.16.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/92315\",\"https://www.cve.org/cverecord?id=CVE-2020-8558\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N\",\"Score\":5.4},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8555\",\"created_at\":\"2020-05-28T16:13:34Z\",\"summary\":\"Half-Blind SSRF in kube-controller-manager\",\"component\":\"k8s.io/controller-manager\",\"details\":\"The Kubernetes kube-controller-manager in versions v1.0-1.14, versions prior to v1.15.12, v1.16.9, v1.17.5, and version v1.18.0 are vulnerable to a Server Side Request Forgery (SSRF) that allows certain authorized users to leak up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network (such as link-local or loopback services).\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.15.12\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/91542\",\"https://www.cve.org/cverecord?id=CVE-2020-8555\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"Score\":6.3},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11254\",\"created_at\":\"2020-03-26T18:55:26Z\",\"summary\":\"kube-apiserver Denial of Service vulnerability from malicious YAML payloads\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.15.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/89535\",\"https://www.cve.org/cverecord?id=CVE-2019-11254\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8552\",\"created_at\":\"2020-03-23T18:35:34Z\",\"summary\":\"apiserver DoS (oom)\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes API server component in versions prior to 1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via successful API requests.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.10\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/89378\",\"https://www.cve.org/cverecord?id=CVE-2020-8552\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\",\"Score\":5.3},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8551\",\"created_at\":\"2020-03-23T18:34:40Z\",\"summary\":\"Kubelet DoS via API\",\"component\":\"k8s.io/kubelet\",\"details\":\"The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.10\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/89377\",\"https://www.cve.org/cverecord?id=CVE-2020-8551\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\",\"Score\":4.3},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11251\",\"created_at\":\"2020-02-03T15:12:22Z\",\"summary\":\"kubectl cp symlink vulnerability\",\"component\":\"k8s.io/kubectl\",\"details\":\"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.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.13.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.0\"},{\"fixed\":\"1.14.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/87773\",\"https://www.cve.org/cverecord?id=CVE-2019-11251\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N\",\"Score\":4.8},\"severity\":\"Medium\"},{\"id\":\"CVE-2018-1002102\",\"created_at\":\"2019-12-03T22:58:37Z\",\"summary\":\"Unvalidated redirect\",\"component\":\"k8s.io/apiserver\",\"details\":\"Improper validation of URL redirection in the Kubernetes API server in versions prior to v1.14.0 allows an attacker-controlled Kubelet to redirect API server requests from streaming endpoints to arbitrary hosts. Impacted API servers will follow the redirect as a GET request with client-certificate credentials for authenticating to the Kubelet.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.14.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/85867\",\"https://www.cve.org/cverecord?id=CVE-2018-1002102\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N\",\"Score\":2.6},\"severity\":\"Low\"},{\"id\":\"CVE-2019-11253\",\"created_at\":\"2019-09-27T16:53:31Z\",\"summary\":\"Kubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attack\",\"component\":\"k8s.io/apiserver\",\"details\":\"Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.13.12\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.0\"},{\"fixed\":\"1.14.8\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/83253\",\"https://www.cve.org/cverecord?id=CVE-2019-11253\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"Score\":7.5},\"severity\":\"High\"},{\"id\":\"CVE-2019-11250\",\"created_at\":\"2019-08-08T02:03:04Z\",\"summary\":\"*** are revealed in logs\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.16.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/81114\",\"https://www.cve.org/cverecord?id=CVE-2019-11250\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11248\",\"created_at\":\"2019-08-06T14:34:33Z\",\"summary\":\"/debug/pprof exposed on kubelet's healthz port\",\"component\":\"k8s.io/kubelet\",\"details\":\"The debugging endpoint /debug/pprof is exposed over the unauthenticated Kubelet healthz port. The go pprof endpoint is exposed over the Kubelet's healthz port. This debugging endpoint can potentially leak sensitive information such as internal Kubelet memory addresses and configuration, or for limited denial of service. Versions prior to 1.15.0, 1.14.4, 1.13.8, and 1.12.10 are affected. The issue is of medium severity, but not exposed by the default configuration.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.12.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.13.0\"},{\"fixed\":\"1.13.8\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.0\"},{\"fixed\":\"1.14.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/81023\",\"https://www.cve.org/cverecord?id=CVE-2019-11248\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11249\",\"created_at\":\"2019-08-05T12:44:23Z\",\"summary\":\"Incomplete fixes for CVE-2019-1002101 and CVE-2019-11246, kubectl cp potential directory traversal\",\"component\":\"k8s.io/kubectl\",\"details\":\"The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes runs tar inside the container to create a tar archive, 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. Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.1, 1.2, 1.4, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.13.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.0\"},{\"fixed\":\"1.14.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/80984\",\"https://www.cve.org/cverecord?id=CVE-2019-11249\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N\",\"Score\":4.8},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11247\",\"created_at\":\"2019-08-05T12:44:08Z\",\"summary\":\"API server allows access to custom resources via wrong scope\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.7.0\"},{\"fixed\":\"1.13.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.0\"},{\"fixed\":\"1.14.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.15.0\"},{\"fixed\":\"1.15.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/80983\",\"https://www.cve.org/cverecord?id=CVE-2019-11247\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L\",\"Score\":5},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11245\",\"created_at\":\"2019-05-24T16:14:49Z\",\"summary\":\"container uid changes to root after first restart or if image is already pulled to the node\",\"component\":\"k8s.io/kubelet\",\"details\":\"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.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.13.6\"},{\"last_affected\":\"1.13.6\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.14.2\"},{\"last_affected\":\"1.14.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/78308\",\"https://www.cve.org/cverecord?id=CVE-2019-11245\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L\",\"Score\":4.9},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11243\",\"created_at\":\"2019-04-18T21:31:53Z\",\"summary\":\"rest.AnonymousClientConfig() does not remove the serviceaccount credentials from config created by rest.InClusterConfig()\",\"component\":\"k8s.io/kubernetes\",\"details\":\"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()\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.12.0\"},{\"last_affected\":\"1.12.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.13.0\"},{\"last_affected\":\"1.13.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/76797\",\"https://www.cve.org/cverecord?id=CVE-2019-11243\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N\",\"Score\":3.1},\"severity\":\"Low\"},{\"id\":\"CVE-2019-11244\",\"created_at\":\"2019-04-16T20:14:25Z\",\"summary\":\"`kubectl:-http-cache=\\u003cworld-accessible dir\\u003e` creates world-writeable cached schema files\",\"component\":\"k8s.io/kubectl\",\"details\":\"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.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.8.0\"},{\"fixed\":\"1.15.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/76676\",\"https://www.cve.org/cverecord?id=CVE-2019-11244\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N\",\"Score\":3.3},\"severity\":\"Low\"},{\"id\":\"CVE-2019-1002100\",\"created_at\":\"2019-02-25T19:39:09Z\",\"summary\":\"json-patch requests can exhaust apiserver resources\",\"component\":\"k8s.io/apiserver\",\"details\":\"In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type \\\"json-patch\\\" (e.g. `kubectl patch --type json` or `\\\"Content-Type: application/json-patch+json\\\"`) that consumes excessive resources while processing, causing a Denial of Service on the API Server.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.0.0\"},{\"fixed\":\"1.11.8\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.12.0\"},{\"fixed\":\"1.12.6\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.13.0\"},{\"fixed\":\"1.13.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/74534\",\"https://www.cve.org/cverecord?id=CVE-2019-1002100\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2018-1002105\",\"created_at\":\"2018-11-26T11:07:36Z\",\"summary\":\"proxy request handling in kube-apiserver can leave vulnerable TCP connections\",\"component\":\"k8s.io/apiserver\",\"details\":\"In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.0.0\"},{\"fixed\":\"1.10.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.11.0\"},{\"fixed\":\"1.11.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.12.0\"},{\"fixed\":\"1.12.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/71411\",\"https://www.cve.org/cverecord?id=CVE-2018-1002105\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"Score\":9.8},\"severity\":\"Critical\"},{\"id\":\"CVE-2018-1002101\",\"created_at\":\"2018-07-03T08:06:15Z\",\"summary\":\"smb mount security issue\",\"component\":\"k8s.io/kubernetes\",\"details\":\"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.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.9.0\"},{\"fixed\":\"1.9.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.10.0\"},{\"fixed\":\"1.10.6\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.11.0\"},{\"fixed\":\"1.11.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/65750\",\"https://www.cve.org/cverecord?id=CVE-2018-1002101\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N\",\"Score\":5.9},\"severity\":\"Medium\"},{\"id\":\"CVE-2018-1002100\",\"created_at\":\"2018-03-16T19:24:46Z\",\"summary\":\"Kubectl copy doesn't check for paths outside of it's destination directory.\",\"component\":\"k8s.io/kubectl\",\"details\":\"In Kubernetes versions 1.5.x, 1.6.x, 1.7.x, 1.8.x, and prior to version 1.9.6, the kubectl cp command insecurely handles tar data returned from the container, and can be caused to overwrite arbitrary local files.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.5.0\"},{\"fixed\":\"1.9.6\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/61297\",\"https://www.cve.org/cverecord?id=CVE-2018-1002100\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N\",\"Score\":4.2},\"severity\":\"Medium\"},{\"id\":\"CVE-2017-1002102\",\"created_at\":\"2018-03-05T20:55:20Z\",\"summary\":\"atomic writer volume handling allows arbitrary file deletion in host filesystem\",\"component\":\"k8s.io/kubelet\",\"details\":\"In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using a secret, configMap, projected or downwardAPI volume can trigger deletion of arbitrary files/directories from the nodes where they are running.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.3.0\"},{\"fixed\":\"1.7.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.8.0\"},{\"fixed\":\"1.8.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.9.0\"},{\"fixed\":\"1.9.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/60814\",\"https://www.cve.org/cverecord?id=CVE-2017-1002102\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H\",\"Score\":7.1},\"severity\":\"High\"},{\"id\":\"CVE-2017-1002101\",\"created_at\":\"2018-03-05T20:53:58Z\",\"summary\":\"subpath volume mount handling allows arbitrary file access in host filesystem\",\"component\":\"k8s.io/kubernetes\",\"details\":\"In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with any volume type (including non-privileged pods, subject to file permissions) can access files/directories outside of the volume, including the host's filesystem.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.3.0\"},{\"fixed\":\"1.7.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.8.0\"},{\"fixed\":\"1.8.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.9.0\"},{\"fixed\":\"1.9.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/60813\",\"https://www.cve.org/cverecord?id=CVE-2017-1002101\"],\"cvssv3\":{\"Vector\":\"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"Score\":8.8},\"severity\":\"High\"}]"
233:  actual  : "[{\"id\":\"CVE-2023-2431\",\"created_at\":\"2023-06-15T14:42:32Z\",\"summary\":\"Bypass of seccomp profile enforcement \",\"component\":\"k8s.io/kubelet\",\"details\":\"A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"fixed\":\"1.25.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"fixed\":\"1.26.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"fixed\":\"1.27.1\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118690\",\"https://www.cve.org/cverecord?id=CVE-2023-2431\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N\",\"Score\":3.4},\"severity\":\"Low\"},{\"id\":\"CVE-2023-2727\",\"created_at\":\"2023-06-13T14:42:06Z\",\"summary\":\"Bypassing policies imposed by the ImagePolicyWebhook and bypassing mountable secrets policy imposed by the ServiceAccount admission plugin\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may be able to launch containers using images that are restricted by ImagePolicyWebhook when using ephemeral containers. Kubernetes clusters are only affected if the ImagePolicyWebhook admission plugin is used together with ephemeral containers.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"last_affected\":\"1.26.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"last_affected\":\"1.27.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118640\",\"https://www.cve.org/cverecord?id=CVE-2023-2727, CVE-2023-2728\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2023-2728\",\"created_at\":\"2023-06-13T14:42:06Z\",\"summary\":\"Bypassing policies imposed by the ImagePolicyWebhook and bypassing mountable secrets policy imposed by the ServiceAccount admission plugin\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.26.0\"},{\"last_affected\":\"1.26.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.27.0\"},{\"last_affected\":\"1.27.2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118640\",\"https://www.cve.org/cverecord?id=CVE-2023-2727, CVE-2023-2728\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2023-2878\",\"created_at\":\"2023-06-02T19:03:54Z\",\"summary\":\"secrets-store-csi-driver discloses service account tokens in logs\",\"component\":\"sigs.k8s.io/secrets-store-csi-driver\",\"details\":\"Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"fixed\":\"1.3.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/118419\",\"https://www.cve.org/cverecord?id=CVE-2023-2878\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2022-3294\",\"created_at\":\"2022-11-08T21:33:26Z\",\"summary\":\"Node address isn't always verified when proxying\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"last_affected\":\"1.23.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.15\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/113757\",\"https://www.cve.org/cverecord?id=CVE-2022-3294\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H\",\"Score\":6.6},\"severity\":\"Medium\"},{\"id\":\"CVE-2022-3162\",\"created_at\":\"2022-11-08T21:33:07Z\",\"summary\":\"Unauthorized read of Custom Resources\",\"component\":\"k8s.io/apiserver\",\"details\":\"Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"last_affected\":\"1.23.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.15\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/113756\",\"https://www.cve.org/cverecord?id=CVE-2022-3162\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2022-3172\",\"created_at\":\"2022-09-16T13:14:50Z\",\"summary\":\"Aggregated API server can cause clients to be redirected (SSRF)\",\"component\":\"/apiserver\",\"details\":\"A security issue was discovered in kube-apiserver that allows an \\naggregated API server to redirect client traffic to any URL.  This could\\n lead to the client performing unexpected actions as well as forwarding \\nthe client's API server credentials to third parties.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.25.0\"},{\"last_affected\":\"1.25.0\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"last_affected\":\"1.24.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"last_affected\":\"1.23.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"0\"},{\"last_affected\":\"1.21.14\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/112513\",\"https://www.cve.org/cverecord?id=CVE-2022-3172\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L\",\"Score\":5.1},\"severity\":\"Medium\"},{\"id\":\"CVE-2021-25749\",\"created_at\":\"2022-09-01T21:02:01Z\",\"summary\":\"`runAsNonRoot` logic bypass for Windows containers\",\"component\":\"k8s.io/kubelet\",\"details\":\"Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"fixed\":\"1.22.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.23.0\"},{\"fixed\":\"1.23.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.24.0\"},{\"fixed\":\"1.24.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/112192\",\"https://www.cve.org/cverecord?id=CVE-2021-25749\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"Score\":7.8},\"severity\":\"High\"},{\"id\":\"CVE-2021-25741\",\"created_at\":\"2021-09-13T20:58:56Z\",\"summary\":\"Symlink Exchange Can Allow Host Filesystem Access\",\"component\":\"k8s.io/kubelet\",\"details\":\"A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files \\u0026 directories outside of the volume, including on the host filesystem.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.14\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.21.0\"},{\"last_affected\":\"1.21.4\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.22.0\"},{\"last_affected\":\"1.22.1\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/104980\",\"https://www.cve.org/cverecord?id=CVE-2021-25741\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"Score\":8.8},\"severity\":\"High\"},{\"id\":\"CVE-2021-25737\",\"created_at\":\"2021-05-18T19:14:27Z\",\"summary\":\"Holes in EndpointSlice Validation Enable Host Network Hijack\",\"component\":\"k8s.io/apiserver\",\"details\":\"A security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.18\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.6\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.21.0\"},{\"last_affected\":\"1.21.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/102106\",\"https://www.cve.org/cverecord?id=CVE-2021-25737\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N\",\"Score\":2.7},\"severity\":\"Low\"},{\"id\":\"CVE-2021-25735\",\"created_at\":\"2021-03-10T18:18:01Z\",\"summary\":\"Validating Admission Webhook does not observe some previous fields\",\"component\":\"k8s.io/apiserver\",\"details\":\"A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. Clusters are only affected by this vulnerability if they run a Validating Admission Webhook for Nodes that denies admission based at least partially on the old state of the Node object. Validating Admission Webhook does not observe some previous fields.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.17\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"last_affected\":\"1.20.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/100096\",\"https://www.cve.org/cverecord?id=CVE-2021-25735\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H\",\"Score\":6.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8566\",\"created_at\":\"2020-10-15T22:07:53Z\",\"summary\":\"Ceph RBD adminSecrets exposed in logs when loglevel \\u003e= 4\",\"component\":\"k8s.io/controller-manager\",\"details\":\"In Kubernetes clusters using Ceph RBD as a storage provisioner, with logging level of at least 4, Ceph RBD admin secrets can be written to logs. This occurs in kube-controller-manager's logs during provisioning of Ceph RBD persistent claims. This affects \\u003c v1.19.3, \\u003c v1.18.10, \\u003c v1.17.13.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.13\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95624\",\"https://www.cve.org/cverecord?id=CVE-2020-8566\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8565\",\"created_at\":\"2020-10-15T22:05:32Z\",\"summary\":\"Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel \\u003e= 9\",\"component\":\"k8s.io/kubectl\",\"details\":\"In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects \\u003c= v1.19.3, \\u003c= v1.18.10, \\u003c= v1.17.13, \\u003c v1.20.0-alpha2.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"last_affected\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"last_affected\":\"1.17.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.20.0\"},{\"fixed\":\"1.20.0-alpha2\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95623\",\"https://www.cve.org/cverecord?id=CVE-2020-8565\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8564\",\"created_at\":\"2020-10-15T22:03:19Z\",\"summary\":\"Docker config secrets leaked when file is malformed and log level \\u003e= 4\",\"component\":\"k8s.io/kubernetes\",\"details\":\"In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects \\u003c v1.19.3, \\u003c v1.18.10, \\u003c v1.17.13.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.10\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.13\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95622\",\"https://www.cve.org/cverecord?id=CVE-2020-8564\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8563\",\"created_at\":\"2020-10-15T22:00:44Z\",\"summary\":\"Secret leaks in kube-controller-manager when using vSphere provider\",\"component\":\"k8s.io/controller-manager\",\"details\":\"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 \\u003c v1.19.3.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.19.0\"},{\"fixed\":\"1.19.3\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/95621\",\"https://www.cve.org/cverecord?id=CVE-2020-8563\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"Score\":4.7},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8557\",\"created_at\":\"2020-07-13T18:39:08Z\",\"summary\":\"Node disk DOS by writing to container /etc/hosts\",\"component\":\"k8s.io/kubelet\",\"details\":\"The Kubernetes kubelet component in versions 1.1-1.16.12, 1.17.0-1.17.8 and 1.18.0-1.18.5 do not account for disk usage by a pod which writes to its own /etc/hosts file. The /etc/hosts file mounted in a pod by kubelet is not included by the kubelet eviction manager when calculating ephemeral storage usage by a pod. If a pod writes a large amount of data to the /etc/hosts file, it could fill the storage space of the node and cause the node to fail.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.16.13\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.6\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/93032\",\"https://www.cve.org/cverecord?id=CVE-2020-8557\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"Score\":5.5},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8559\",\"created_at\":\"2020-07-08T17:03:16Z\",\"summary\":\"Privilege escalation from compromised node to cluster\",\"component\":\"k8s.io/apiserver\",\"details\":\"The Kubernetes kube-apiserver in versions v1.6-v1.15, and versions prior to v1.16.13, v1.17.9 and v1.18.6 are vulnerable to an unvalidated redirect on proxied upgrade requests that could allow an attacker to escalate privileges from a node compromise to a full cluster compromise.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.6.0\"},{\"last_affected\":\"1.16.12\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"last_affected\":\"1.17.8\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.5\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/92914\",\"https://www.cve.org/cverecord?id=CVE-2020-8559\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H\",\"Score\":6.4},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8558\",\"created_at\":\"2020-06-19T18:38:58Z\",\"summary\":\"Node setting allows for neighboring hosts to bypass localhost boundary\",\"component\":\"k8s.io/kubelet\",\"details\":\"The Kubelet and kube-proxy components in versions 1.1.0-1.16.10, 1.17.0-1.17.6, and 1.18.0-1.18.3 were found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service.\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.16.11\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.7\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"fixed\":\"1.18.4\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/92315\",\"https://www.cve.org/cverecord?id=CVE-2020-8558\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N\",\"Score\":5.4},\"severity\":\"Medium\"},{\"id\":\"CVE-2020-8555\",\"created_at\":\"2020-05-28T16:13:34Z\",\"summary\":\"Half-Blind SSRF in kube-controller-manager\",\"component\":\"k8s.io/controller-manager\",\"details\":\"The Kubernetes kube-controller-manager in versions v1.0-1.14, versions prior to v1.15.12, v1.16.9, v1.17.5, and version v1.18.0 are vulnerable to a Server Side Request Forgery (SSRF) that allows certain authorized users to leak up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network (such as link-local or loopback services).\",\"affected\":[{\"ranges\":[{\"events\":[{\"introduced\":\"1.1.0\"},{\"fixed\":\"1.15.12\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.16.0\"},{\"fixed\":\"1.16.9\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.17.0\"},{\"fixed\":\"1.17.5\"}],\"type\":\"SEMVER\"}]},{\"ranges\":[{\"events\":[{\"introduced\":\"1.18.0\"},{\"last_affected\":\"1.18.0\"}],\"type\":\"SEMVER\"}]}],\"references\":[\"https://github.com/kubernetes/kubernetes/issues/91542\",\"https://www.cve.org/cverecord?id=CVE-2020-8555\"],\"cvssv3\":{\"Vector\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"Score\":6.3},\"severity\":\"Medium\"},{\"id\":\"CVE-2019-11254\",\"created_at\":\"2020-03-26T18:55:26Z\",\"summary\":\"kube-apiserver Denial of Service vulnerability from ma...

@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch 3 times, most recently from e2fb7a6 to 704d473 Compare February 15, 2025 03:27
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from 704d473 to 24ab354 Compare February 16, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants