zrok's broken ownership check in DELETE /api/v2/unaccess allows non-admin to delete global frontend records
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.1, the unaccess handler (controller/unaccess.go) contains a logical error in its ownership guard: when a frontend record has environment_id = NULL (the marker for admin-created global frontends), the condition short-circuits to false and allows the deletion to proceed without any ownership verification. A non-admin user who knows a global frontend token can call DELETE /api/v2/unaccess with any of their own environment IDs and permanently delete the global frontend, taking down all public shares routed through it. Version 2.0.1 patches the issue.
From the CVE record · GitHub_M
The zrok unaccess handler fails to verify ownership before deleting an admin-created global frontend. An authenticated non-admin user who knows its token can call the API with one of their own environment IDs to permanently delete the frontend, taking down public shares routed through it. No victim interaction is required.
Check deployments using Go package github.com/openziti/zrok/v2 before 2.0.1 or github.com/openziti/zrok at version 1.1.11 or earlier.