# CVE-2019-11255: Kubernetes CSI volume snapshot, cloning and resizing features can result in unauthorized volume data access or mutation

> Attackers can access or modify PersistentVolume data during CSI operations due to improper input validation in Kubernetes sidecar containers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f4w6-3rh6-6q4q, RHSA-2019:4054, RHSA-2019:4096, RHSA-2019:4225

## What is CVE-2019-11255?

CVE-2019-11255 is a medium-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 5 Dec 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper input validation in Kubernetes CSI sidecar containers for external-provisioner (<v0.4.3, <v1.0.2, v1.1, <v1.2.2, <v1.3.1), external-snapshotter (<v0.4.2, <v1.0.2, v1.1, <1.2.2), and external-resizer (v0.1, v0.2) could result in unauthorized PersistentVolume data access or volume mutation during snapshot, restore from snapshot, cloning and resizing operations.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-11255?

18 open source packages ship an affected version, including github.com/kubernetes-csi/external-provisioner, github.com/kubernetes-csi/external-resizer and github.com/kubernetes-csi/external-snapshotter/v6. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubernetes-csi/external-provisioner` | Go | All versions | None |
| `github.com/kubernetes-csi/external-provisioner` | Go | All versions | None |
| `github.com/kubernetes-csi/external-provisioner` | Go | All versions | 0.4.3 |
| `github.com/kubernetes-csi/external-provisioner` | Go | All versions | 0.4.3 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.0.0 | 1.0.2 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.0.0 | 1.0.2 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.2.0 | 1.2.2 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.2.0 | 1.2.2 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.3.0 | 1.3.1 |
| `github.com/kubernetes-csi/external-provisioner` | Go | From 1.3.0 | 1.3.1 |
| `github.com/kubernetes-csi/external-resizer` | Go | All versions | None |
| `github.com/kubernetes-csi/external-resizer` | Go | All versions | None |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | All versions | None |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | All versions | None |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | From 1.0.0 | 1.0.2 |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | From 1.0.0 | 1.0.2 |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | From 1.2.0 | 1.2.2 |
| `github.com/kubernetes-csi/external-snapshotter/v6` | Go | From 1.2.0 | 1.2.2 |
| `openshift-external-storage` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-cephfs-provisioner` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-debuginfo` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-efs-provisioner` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-local-provisioner` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-manila-provisioner` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-snapshot-controller` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage-snapshot-provisioner` | Red Hat:openshift:3.11::el7 | All versions | 0:0.0.2-10.gitd3c94f0.el7 |
| `openshift-external-storage` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-cephfs-provisioner` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-debuginfo` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-efs-provisioner` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-local-provisioner` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-manila-provisioner` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-snapshot-controller` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-snapshot-provisioner` | Red Hat:openshift:4.1::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-cephfs-provisioner` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-debuginfo` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-efs-provisioner` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-local-provisioner` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |
| `openshift-external-storage-manila-provisioner` | Red Hat:openshift:4.2::el7 | All versions | 0:0.0.2-11.gitd3c94f0.el7 |

Products: Kubernetes External-Provisioner, Kubernetes External-Resizer, Kubernetes External-Snapshotter, Redhat Openshift Container Platform.

## How do I fix CVE-2019-11255?

Upgrade github.com/kubernetes-csi/external-provisioner to a fixed version for your release line: 0.4.3, 1.0.2, 1.2.2 or 1.3.1.

## Is CVE-2019-11255 being exploited?

There is no known exploitation of CVE-2019-11255 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11255 and fix it if it is affected.

What it is: CVE-2019-11255 is a medium-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 5 Dec 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-11255 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubernetes-csi/external-provisioner (Go): affected all versions; no fix listed
- github.com/kubernetes-csi/external-provisioner (Go): affected all versions; no fix listed
- github.com/kubernetes-csi/external-provisioner (Go): affected all versions; fixed in 0.4.3
- github.com/kubernetes-csi/external-provisioner (Go): affected all versions; fixed in 0.4.3
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.0.0; fixed in 1.0.2
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.0.0; fixed in 1.0.2
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.2.0; fixed in 1.2.2
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.2.0; fixed in 1.2.2
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.3.0; fixed in 1.3.1
- github.com/kubernetes-csi/external-provisioner (Go): affected from 1.3.0; fixed in 1.3.1
- github.com/kubernetes-csi/external-resizer (Go): affected all versions; no fix listed
- github.com/kubernetes-csi/external-resizer (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11255/ (Markdown: https://insights.sbomify.com/CVE-2019-11255/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11255
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11255
- OSV: https://osv.dev/vulnerability/CVE-2019-11255

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11255/
Summaries are generated and may contain mistakes; the official description above is the record.