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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: kubernetes
Published: 2021-01-21T17:09:21.567240Z
Updated: 2024-09-17T01:47:07.863Z
Reserved: 2020-02-03T00:00:00
Link: CVE-2020-8569
Vulnrichment
No data.
NVD
Status : Modified
Published: 2021-01-21T17:15:14.250
Modified: 2024-11-21T05:39:03.003
Link: CVE-2020-8569
Redhat