GSD-2020-8569
Vulnerability from gsd - Updated: 2023-12-13 01:21Details
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.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2020-8569",
"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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.",
"id": "GSD-2020-8569",
"references": [
"https://www.suse.com/security/cve/CVE-2020-8569.html"
]
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2020-8569"
],
"details": "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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.",
"id": "GSD-2020-8569",
"modified": "2023-12-13T01:21:54.223623Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security@kubernetes.io",
"DATE_PUBLIC": "2020-11-17T21:00:00.000Z",
"ID": "CVE-2020-8569",
"STATE": "PUBLIC",
"TITLE": "Kubernetes CSI snapshot-controller DoS"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "CSI Snapshotter",
"version": {
"version_data": [
{
"version_affected": "\u003c=",
"version_name": "snapshot-controller v3.0",
"version_value": "v3.0.1"
},
{
"version_affected": "\u003c=",
"version_name": "snapshot-controller v2.1",
"version_value": "v2.1.2"
}
]
}
}
]
},
"vendor_name": "Kubernetes"
}
]
}
},
"credit": [
{
"lang": "eng",
"value": "Qin Ping"
}
],
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected."
}
]
},
"generator": {
"engine": "Vulnogram 0.0.9"
},
"impact": {
"cvss": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-476 NULL Pointer Dereference"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU",
"refsource": "MISC",
"url": "https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU"
},
{
"name": "https://github.com/kubernetes-csi/external-snapshotter/issues/380",
"refsource": "MISC",
"url": "https://github.com/kubernetes-csi/external-snapshotter/issues/380"
}
]
},
"source": {
"defect": [
"https://github.com/kubernetes-csi/external-snapshotter/issues/380"
],
"discovery": "INTERNAL"
},
"work_around": [
{
"lang": "eng",
"value": "Prior to upgrading, this vulnerability can be mitigated by restricting creation of VolumeSnapshot custom resources in API group snapshot.storage.k8s.io only to trusted users."
}
]
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003e=2.1.0 \u003c2.1.3||\u003e=3.0.0 \u003c3.0.2",
"affected_versions": "All versions starting from 2.1.0 before 2.1.3, all versions starting from 3.0.0 before 3.0.2",
"cvss_v2": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-476",
"CWE-937"
],
"date": "2021-02-01",
"description": "Kubernetes CSI snapshot-controller. When exploited, users can\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.",
"fixed_versions": [
"2.1.3",
"3.0.2"
],
"identifier": "CVE-2020-8569",
"identifiers": [
"CVE-2020-8569"
],
"not_impacted": "",
"package_slug": "go/github.com/kubernetes-csi/external-snapshotter",
"pubdate": "2021-01-21",
"solution": "Unfortunately, there is no solution available yet.",
"title": "NULL Pointer Dereference",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2020-8569"
],
"uuid": "35c00e66-437d-49a2-a3d9-1d86ed4f99f7"
},
{
"affected_range": "\u003e=v2.0.0 \u003cv2.1.3",
"affected_versions": "All versions starting from 2.0.0 before 2.1.3",
"cvss_v2": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-476",
"CWE-937"
],
"date": "2022-04-20",
"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 does 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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.",
"fixed_versions": [
"v2.1.3"
],
"identifier": "CVE-2020-8569",
"identifiers": [
"GHSA-hwrr-rhmm-vcvf",
"CVE-2020-8569"
],
"not_impacted": "All versions before 2.0.0, all versions starting from 2.1.3",
"package_slug": "go/github.com/kubernetes-csi/external-snapshotter/v2",
"pubdate": "2022-02-15",
"solution": "Upgrade to version 2.1.3 or above.",
"title": "NULL Pointer Dereference",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2020-8569",
"https://github.com/kubernetes-csi/external-snapshotter/issues/380",
"https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU",
"https://github.com/advisories/GHSA-hwrr-rhmm-vcvf"
],
"uuid": "55ee98bf-0d7e-4c75-be7b-93a9ebcb4acd",
"versions": [
{
"commit": {
"sha": "fd8d8a33ddb591fc06197879fb9b4cc6ad7e753a",
"tags": [
"v2.0.0"
],
"timestamp": "20200106204216"
},
"number": "v2.0.0"
},
{
"commit": {
"sha": "7819ee35f860bc370043d875ad6ca09d9fae25dc",
"tags": [
"v2.1.3"
],
"timestamp": "20201211184926"
},
"number": "v2.1.3"
}
]
},
{
"affected_range": "\u003e=v3.0.0 \u003cv3.0.2",
"affected_versions": "All versions starting from 3.0.0 before 3.0.2",
"cvss_v2": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-476",
"CWE-937"
],
"date": "2022-04-20",
"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 does 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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.",
"fixed_versions": [
"v3.0.2"
],
"identifier": "CVE-2020-8569",
"identifiers": [
"GHSA-hwrr-rhmm-vcvf",
"CVE-2020-8569"
],
"not_impacted": "All versions before 3.0.0, all versions starting from 3.0.2",
"package_slug": "go/github.com/kubernetes-csi/external-snapshotter/v3",
"pubdate": "2022-02-15",
"solution": "Upgrade to version 3.0.2 or above.",
"title": "NULL Pointer Dereference",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2020-8569",
"https://github.com/kubernetes-csi/external-snapshotter/issues/380",
"https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU",
"https://github.com/advisories/GHSA-hwrr-rhmm-vcvf"
],
"uuid": "22b28f72-0e18-46ed-9f4f-b9b1fd52b0d0",
"versions": [
{
"commit": {
"sha": "28abcf95d113040090082d2f948c07c53566e36a",
"tags": [
"client/v3.0.0",
"v3.0.0"
],
"timestamp": "20200917164845"
},
"number": "v3.0.0"
},
{
"commit": {
"sha": "271a825f20dbb75b11184d84fddc44e7d12cf943",
"tags": [
"v3.0.2"
],
"timestamp": "20201031195051"
},
"number": "v3.0.2"
}
]
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:kubernetes:container_storage_interface_snapshotter:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "2.1.3",
"versionStartIncluding": "2.1.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:kubernetes:container_storage_interface_snapshotter:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "3.0.2",
"versionStartIncluding": "3.0.0",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "security@kubernetes.io",
"ID": "CVE-2020-8569"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "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\u2019t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-476"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "N/A",
"refsource": "MLIST",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU"
},
{
"name": "N/A",
"refsource": "CONFIRM",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/kubernetes-csi/external-snapshotter/issues/380"
}
]
}
},
"impact": {
"baseMetricV2": {
"acInsufInfo": false,
"cvssV2": {
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "SINGLE",
"availabilityImpact": "PARTIAL",
"baseScore": 4.0,
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
"version": "2.0"
},
"exploitabilityScore": 8.0,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"userInteractionRequired": false
},
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6
}
},
"lastModifiedDate": "2021-02-01T19:05Z",
"publishedDate": "2021-01-21T17:15Z"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…