CVE-2020-8569

low-risk

Published 2021-01-21

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.

Do I need to act?

0.35% chance of exploitation

EPSS score — low exploit probability

Not on CISA KEV list

No confirmed active exploitation reported to CISA

Patch status unknown

Check vendor advisories for fix availability and mitigation guidance

CVSS 4.3/10 Medium

NETWORK / LOW complexity

Affected Products (1)

Container Storage Interface Snapshotter

Affected Vendors

Kubernetes

References (4)

Exploit https://github.com/kubernetes-csi/external-snapshotter/issues/380

Mailing List https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU

Exploit https://github.com/kubernetes-csi/external-snapshotter/issues/380

Mailing List https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU

/ 100

low-risk

Severity 18/34 · Moderate

Exploitability 1/34 · Minimal

Exposure 5/34 · Minimal