CVE-2020-8569
Summary
| CVE | CVE-2020-8569 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-01-21 17:15:00 UTC |
| Updated | 2021-02-01 19:05:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-476
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Kubernetes | Container Storage Interface Snapshotter | All | All | All | All |
| Application | Kubernetes | Container Storage Interface Snapshotter | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Fwd: [Security Advisory] [CSI snapshot-controller] CVE-2020-8569: snapshot-controller DoS | MLIST | groups.google.com | Mailing List, Third Party Advisory |
| snapshot-controller panics when source PVC does not exist · Issue #380 · kubernetes-csi/external-snapshotter · GitHub | CONFIRM | github.com | Exploit, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
LEGACY: Qin Ping
There are currently no legacy QID mappings associated with this CVE.