Skip to content

NULL Pointer Dereference in Kubernetes CSI snapshot-controller

Moderate severity GitHub Reviewed Published Feb 15, 2022 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

gomod github.com/kubernetes-csi/external-snapshotter/v2 (Go)

Affected versions

>= 2.0.0, < 2.1.3

Patched versions

2.1.3
gomod github.com/kubernetes-csi/external-snapshotter/v3 (Go)
>= 3.0.0, < 3.0.2
3.0.2

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.

References

Reviewed May 12, 2021
Published to the GitHub Advisory Database Feb 15, 2022
Last updated Jan 9, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.066%
(31st percentile)

Weaknesses

CVE ID

CVE-2020-8569

GHSA ID

GHSA-hwrr-rhmm-vcvf

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.