GHSA-74m3-9qvm-rp9h is a high-severity (CVSS 8.7) vulnerability in github.com/openziti/zrok. O3 Security confirms whether GHSA-74m3-9qvm-rp9h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
zrok: WebDAV drive backend follows symlinks outside DriveRoot, enabling host filesystem read/write
Real-World Exposure
github.com/openziti/zrok🐹github.com/openziti/zrok/v2Real-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
Summary The zrok WebDAV drive backend (davServer.Dir) restricts path traversal through lexical normalization but does not prevent symlink following. When a symbolic link inside the shared DriveRoot points to a location outside that root, remote WebDAV consumers can read files and—on shares without OS-level permission restrictions—write or overwrite files anywhere on the host filesystem accessible to the zrok process.
- Attack Vector: Network — exploitation is performed entirely over the WebDAV endpoint; the attacker issues HTTP requests to the public zrok share URL.
- Attack Complexity: High — a precondition outside the attacker's direct control must hold: a symlink pointing outside DriveRoot must already exist within it (created locally, not via WebDAV).
- Privileges Required: None — zrok share public --backend-mode drive exposes the WebDAV endpoint with no authentication by default.
- User Interaction: None — once the symlink precondition is met, exploitation requires no user interaction.
- Scope: Changed — the vulnerability allows an attacker to escape the WebDAV root (the security boundary) and access the broader host filesystem.
- Confidentiality Impact: High — arbitrary files readable by the zrok process can be retrieved.
- Integrity Impact: High — the WebDAV PUT handler opens files with O_RDWR|O_CREATE|O_TRUNC, meaning symlink targets outside DriveRoot can be overwritten (e.g. ~/.ssh/authorized_keys).
- Availability Impact: None — no direct availability impact.
Affected Components
- drives/davServer/file.go — Dir.OpenFile (line 140), Dir.Stat (line 176), Dir.Mkdir (line 133), Dir.RemoveAll (line 151)
- endpoints/drive/backend.go — NewBackend (line 51–52)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openziti/zrok | all versions | No fix |
| 🐹Go | github.com/openziti/zrok/v2 | all versions | 2.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openziti/zrok. 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
No patched version of github.com/openziti/zrok has shipped for GHSA-74m3-9qvm-rp9h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-74m3-9qvm-rp9h 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-74m3-9qvm-rp9h. 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-74m3-9qvm-rp9h in your dependencies?
O3 detects GHSA-74m3-9qvm-rp9h across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.