CVE-2020-8569
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.
EPSS 2.27% · 82.2th percentile
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | CSI Snapshotter | snapshot-controller v2.1, * |
| github.com | kubernetes-csi/external-snapshotter/v3 | 3.0.0 |
| github.com | kubernetes-csi/external-snapshotter/v2 | 2.0.0 |
| kubernetes | container_storage_interface_snapshotter | 2.1.0, 3.0.0 |
Timeline
- CVE Published
- Dec 3, 2020 PoC Published
- Apr 14, 2021 EPSS Score
- Jun 23, 2021 EPSS Score
- Aug 25, 2021 EPSS Score
- Dec 28, 2021 EPSS Score
- Jan 6, 2022 EPSS Score
- Feb 4, 2022 EPSS Score
- Mar 1, 2022 EPSS Score
- May 3, 2022 EPSS Score
- Jul 4, 2022 EPSS Score
- Sep 6, 2022 EPSS Score