Kubernetes CSI snapshot-controller DoS
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.3, 3.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes CSI Snapshotter
From snapshot-controller v3.0 · through v3.0.1; From snapshot-controller v2.1 · through v2.1.2
- github.com/kubernetes-csi/external-snapshotter/v2Go
From 2.0.0 · fixed in 2.1.3
- github.com/kubernetes-csi/external-snapshotter/v3Go
From 3.0.0 · fixed in 3.0.2