Nezha
Nezha Monitoring: Cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Nezha versions 1.14.13 through 1.14.14 and 2.0.0 through 2.0.9 do not bind stream identifiers created by CreateStream in service/rpc/io_stream.go to their creating user, and `GET /ws/terminal/:id` and `GET /ws/file/:id` only check whether the supplied UUID exists. An authenticated RoleMember who obtains a live stream UUID from logs, browser history, referer data, or telemetry can attach to another user's terminal or file-manager session, read and write target-server files, and execute shell commands. This issue is fixed in version 2.0.10.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.14.13, <= 1.14.14
- >= 2.0.0, < 2.0.10
Fixed in 2.0.10
Mitigation
Upgrade nezha to 2.0.10 or later.
References
- Vendor advisory github.com/nezhahq/nezha/security/advisories/G…
- Patch github.com/nezhahq/nezha/commit/6661d6a7fc1c26…
- Release notes github.com/nezhahq/nezha/releases/tag/v2.0.10
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.