CVE-2020-8569: Kubernetes CSI snapshot-controller DoS
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, is automatically restarted by Kubernetes, and processes the same VolumeSnapshot custom resource after the restart, entering an endless crashloop. Only the volume snapshot feature is affected by this vulnerability. When exploited, users can’t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID of this vulnerability?
The vulnerability ID is CVE-2020-8569.
What is the severity of CVE-2020-8569?
The severity of CVE-2020-8569 is medium.
What software versions are affected by CVE-2020-8569?
Kubernetes CSI snapshot-controller versions prior to v2.1.3 and v3.0.2 are affected.
How can this vulnerability be exploited?
This vulnerability can be exploited when processing a VolumeSnapshot custom resource with certain conditions.
Are there any references for further information on this vulnerability?
Yes, you can refer to the following links: [Link 1](https://github.com/kubernetes-csi/external-snapshotter/issues/380) [Link 2](https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU)