GHSA-6x26-5727-rrm9 Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host
SummaryAn authenticated Nezha dashboard user can create or update a DDNS profile with provider `webhook` and configure an arbitrary `webhook_url`, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with `utils.HttpClient` without the SSRF protections used by notification webhooks.This allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive.DetailsThe DDNS API is available to authenticated users, not only administrators:`cmd/dashboard/controller/controller.go:137` registers `GET /api/v1/ddns`.`cmd/dashboard/controller/controller.go:139` registers `POST /api/v1/ddns`.`cmd/dashboard/controller/controller.go:140` registers `PATCH /api/v1/ddns/:id`.The create and update handlers copy attacker-controlled webhook fields directly from JSON request bodies into `model.DDNSProfile`:`cmd/dashboard/controller/ddns.go:47-74` accepts `model.DDNSForm` and stores `WebhookURL`, `WebhookMethod`, `WebhookRequestType`, `WebhookRequestBody`, and `WebhookHeaders`.`cmd/dashboard/controller/ddns.go:112-145` updates the same fields after profile ownership is checked.`model/ddns_api.go:11-15` exposes these fields as JSON input.`model/ddns.go:28-33` stores these fields on the persisted profile.Users can attach owned DDNS profiles to owned servers, and DDNS updates are triggered in common server update and agent IP-reporting paths:`cmd/dashboard/controller/server.go:63-83` checks DDNS profile ownership, then stores `EnableDDNS`, `DDNSProfiles`, and `OverrideDDNSDomains` on an owned server.`service/singleton/server.go:44-58` calls `UpdateDDNS` when a server with DDNS enabled is updated.`service/rpc/nezha.go:247-279` calls `UpdateDDNS` when an authenticated agent reports a changed IP.The DDNS provider dispatcher instantiates the webhook provider when `Provider == "webhook"`:`service/singleton/ddns.go:58-95`, especially `service/singleton/ddns.go:79-81`.The sink is the DDNS webhook provider:`pkg/ddns/webhook/webhook.go:49-65` prepares and sends the HTTP request with `utils.HttpClient.Do(req)`.`pkg/ddns/webhook/webhook.go:85-100` formats and applies attacker-controlled headers.`pkg/ddns/webhook/webhook.go:91-92` creates the request with the configured method and URL.`pkg/ddns/webhook/webhook.go:117-134` parses the configured URL and only formats query parameters; it does not restrict scheme, host, IP range, or redirects.`pkg/ddns/webhook/webhook.go:137-158` builds attacker-controlled request bodies for POST/PATCH/PUT.The project already contains SSRF defenses for notification webhooks, showing the expected mitigation pattern is absent from the DDNS webhook path:`model/notification.go:34-58` defines blocked private/reserved CIDRs.`model/notification.go:193-221` creates a notification HTTP client that resolves and pins a validated IP and disables redirects.`model/notification.go:229-263` only allows `http`/`https`, requires a hostname, resolves all addresses, and rejects disallowed IPs.`model/notification.go:265-276` rejects blocked ranges and non-global-unicast targets.Equivalent validation was not found in `pkg/ddns/webhook/webhook.go`.Safe local PoCEnvironment:Repository: `https://github.com/nezhahq/nezha.git`Commit tested: `05e5da2535197fc223b79601d50eeea362dcf853`Tag at commit: `v2.0.9`Module: `github.com/nezhahq/nezha`Go version: `go1.26.3 linux/amd64`Testing scope: local-only; loopback HTTP listener and fake local UDP DNS SOA server only.A temporary same-package test was created and removed automatically after execution. It used a local `httptest` listener as the internal service and a local UDP DNS server that returned an SOA for `example.com.`. The test then executed the normal DDNS update pipeline with a webhook DDNS profile pointing at the loopback HTTP listener.Command run:Observed output:A lower-level provider-only confirmation was also run with `go test ./pkg/ddns/webhook -run TestLocalPoCDDNSWebhookReachesLoopback -v` and observed:Cleanup:Both temporary PoC test files were removed by shell `trap`.`find . -path './.git' -prune -o \( -name 'ssrf_local_poc_test.go' -o -name 'ddns_ssrf_local_poc_test.go' \) -print` returned no files.ImpactAn authenticated dashboard user can cause the Nezha dashboard process to send arbitrary HTTP requests to services reachable from the dashboard host, including loopback and private network targets. The confirmed path allows attacker-controlled method, URL path/query, headers, and request body.Potential impacts depend on deployment and reachable internal services, but include:Blind probing of internal HTTP services from the dashboard network location.Triggering state-changing internal endpoints that trust localhost or private network origins.Reaching services not exposed to the attacker directly.Interaction with cloud metadata or control-plane endpoints if reachable and not otherwise protected.The response body is not returned to the attacker in the confirmed code path, so this should not be described as direct arbitrary internal file/secret read without an additional response-disclosure primitive.
CVSS v3.1 score: 6.4