Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2019-11255

MEDIUM

Kubernetes CSI Sidecar Containers Can Allow Unauthorized Data Access

Also known asGHSA-f4w6-3rh6-6q4q
Published
Dec 5, 2019
Updated
Apr 10, 2026
Affected
10 pkgs
Patched
6 / 10
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk75th percentile+0.95%
0.20%0.89%1.57%2.25%0.7%1.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

10 pkgs affected
🐹github.com/kubernetes-csi/external-provisioner🐹github.com/kubernetes-csi/external-provisioner🐹github.com/kubernetes-csi/external-provisioner🐹github.com/kubernetes-csi/external-provisioner🐹github.com/kubernetes-csi/external-provisioner🐹github.com/kubernetes-csi/external-snapshotter/v6🐹github.com/kubernetes-csi/external-snapshotter/v6🐹github.com/kubernetes-csi/external-snapshotter/v6+2 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

10 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubernetes-csi/external-provisionerall versions0.4.3
🐹Gogithub.com/kubernetes-csi/external-provisioner1.0.0&&< 1.0.21.0.2
🐹Gogithub.com/kubernetes-csi/external-provisionerall versionsNo fix
🐹Gogithub.com/kubernetes-csi/external-provisioner1.2.0&&< 1.2.21.2.2
🐹Gogithub.com/kubernetes-csi/external-provisioner1.3.0&&< 1.3.11.3.1
🐹Gogithub.com/kubernetes-csi/external-snapshotter/v61.0.0&&< 1.0.21.0.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes-csi/external-provisioner. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/kubernetes-csi/external-provisioner to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11255 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2019-11255 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2019-11255. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2019-11255 in your dependencies?

O3 detects CVE-2019-11255 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.