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…
Does this matter?
Lower severity and a low EPSS score (2.27%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 2.27% probability · 82th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-476
- Affected
- kubernetes/container storage interface snapshotter
- Source
- jordan@liggitt.net
References
- https://github.com/kubernetes-csi/external-snapshotter/issues/380Exploit, Third Party Advisory
- https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxUMailing List, Third Party Advisory
- https://github.com/kubernetes-csi/external-snapshotter/issues/380Exploit, Third Party Advisory
- https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxUMailing List, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.