GHSA-hwrr-rhmm-vcvf
MEDIUMGHSA-hwrr-rhmm-vcvf is a medium-severity (CVSS 6.5) NULL Pointer Dereference vulnerability in github.com/kubernetes-csi/external-snapshotter/v2. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-hwrr-rhmm-vcvf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
NULL Pointer Dereference in Kubernetes CSI snapshot-controller
Real-World Exposure
github.com/kubernetes-csi/external-snapshotter/v2🐹github.com/kubernetes-csi/external-snapshotter/v3Real-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kubernetes-csi/external-snapshotter/v2 | ≥ 2.0.0&&< 2.1.3 | 2.1.3 |
| 🐹Go | github.com/kubernetes-csi/external-snapshotter/v3 | ≥ 3.0.0&&< 3.0.2 | 3.0.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes-csi/external-snapshotter/v2. 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.
Fix
Update github.com/kubernetes-csi/external-snapshotter/v2 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwrr-rhmm-vcvf is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-hwrr-rhmm-vcvf 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 GHSA-hwrr-rhmm-vcvf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hwrr-rhmm-vcvf in your dependencies?
O3 detects GHSA-hwrr-rhmm-vcvf across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.