Kubernetes CSI snapshot-controller DoS
Kubernetes CSI Snapshotter
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes-csi/external-snapshotter/v2 Go |
|
|
| github.com/kubernetes-csi/external-snapshotter/v3 Go |
|
|
Kubernetes CSI Snapshotter
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes-csi/external-snapshotter/v2 Go |
|
|
| github.com/kubernetes-csi/external-snapshotter/v3 Go |
|
|
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.
From the CVE record · kubernetes
The snapshot-controller can enter an endless crashloop when it processes a VolumeSnapshot that references a nonexistent PersistentVolumeClaim and no VolumeSnapshotClass. Someone able to submit such a resource can prevent users from taking or deleting volume snapshots. Other Kubernetes functionality is unaffected.
Teams running Kubernetes CSI Snapshotter with Go package github.com/kubernetes-csi/external-snapshotter/v2 versions >=2.0.0 and <2.1.3, or github.com/kubernetes-csi/external-snapshotter/v3 versions >=3.0.0 and <3.0.2, should check their deployments.