Skip to content
Fencer Intel
medium 4.3

CVE-2020-8569 json

Kubernetes CSI snapshot-controller DoS

published 5y ago modified 4mo ago also GHSA-hwrr-rhmm-vcvf , EUVD-2022-1057

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

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.

Patch / fix

  • go github.com/kubernetes-csi/external-snapshotter/v2 2.1.3
  • go github.com/kubernetes-csi/external-snapshotter/v3 3.0.2
  • kubernetes container_storage_interface_snapshotter 2.1.3, 3.0.2

Is CVE-2020-8569 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-8569 updated cvss 5.3

kubernetes-csi: NULL pointer dereference in snapshot-controller when processing a VolumeSnapshot custom resource

  • Red Hat OpenShift Container Platform 4 openshift4/ose-csi-snapshot-controller-rhel8, openshift4/ose-csi-external-snapshotter-rhel9 Red Hat OpenShift Virtualization 2 virt-controller, virt-cdi-controller, hyperconverged-cluster-operator
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.21% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/kubernetes-csi/external-snapshotter/issues/380 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/kubernetes-csi/external-snapshotter/v2
>=2.0.0, <2.1.3
2.1.3
go github.com/kubernetes-csi/external-snapshotter/v3
>=3.0.0, <3.0.2
3.0.2

Affected products

  • Kubernetes CSI Snapshotter

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.