Container Storage Interface Snapshotter vulnerabilitiesRanked by how likely they are to be used.
Container Storage Interface Snapshotter is made by Kubernetes. We track 1 published vulnerability in it, across 21 versions. None of them is on the list of flaws known to be exploited today. If you run Container Storage Interface Snapshotter, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Container Storage Interface Snapshotter vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Container Storage Interface Snapshotter's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Container Storage Interface Snapshotter flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.3%CVE-2020-8569Medium
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...
Running Container Storage Interface Snapshotter? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Container Storage Interface Snapshotter on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Container Storage Interface Snapshotter, across 21 versions.
None of Container Storage Interface Snapshotter's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Container Storage Interface Snapshotter. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.