zrok: WebDAV drive backend follows symlinks outside DriveRoot, enabling host filesystem read/write
openziti zrok
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openziti/zrok Go |
| No fix yet |
| github.com/openziti/zrok/v2 Go |
|
|
openziti zrok
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openziti/zrok Go |
| No fix yet |
| github.com/openziti/zrok/v2 Go |
|
|
zrok is software for sharing web services, files, and network resources. Prior to version 2.0.2, 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. This issue has been patched in version 2.0.2.
From the CVE record · GitHub_M
The zrok WebDAV drive backend follows symbolic links inside a shared DriveRoot even when they point outside it. Remote WebDAV consumers can read files accessible to the zrok process and, on shares without OS-level permission restrictions, write or overwrite them.
Check deployments using Go package github.com/openziti/zrok/v2 before 2.0.2 or github.com/openziti/zrok at version 1.1.11 or earlier; no fix is listed for the latter package.