Cloudreve before 4.17.0 SSRF via Admin.Read OAuth scope
cloudreve
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cloudreve/Cloudreve/v4 Go |
|
|
| github.com/cloudreve/Cloudreve/v3 Go |
| No fix yet |
cloudreve
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cloudreve/Cloudreve/v4 Go |
|
|
| github.com/cloudreve/Cloudreve/v3 Go |
| No fix yet |
|
| No fix yet |
Cloudreve before 4.17.0 registers the administrative node test endpoints (POST /api/v4/admin/node/test and POST /api/v4/admin/node/test/downloader) without requiring the Admin.Write OAuth scope, unlike the node create/update/delete routes. An OAuth client that has been authorized by an administrator with only the Admin.Read scope can therefore submit attacker-controlled node definitions and cause the Cloudreve server to issue outbound requests to arbitrary URLs, enabling blind server-side request forgery, internal service probing, and delivery of signed Cloudreve slave-style requests to attacker-chosen endpoints.
From the CVE record · VulnCheck
Cloudreve before 4.17.0 does not require the Admin.Write OAuth scope for its administrative node test endpoints. An OAuth client authorized by an administrator with only Admin.Read can submit node definitions that make the server send requests to attacker-chosen URLs, enabling blind server-side request forgery and internal service probing.
Operators using Cloudreve before 4.17.0 or the affected Go packages github.com/cloudreve/Cloudreve/v4, github.com/cloudreve/Cloudreve/v3, and github.com/cloudreve/Cloudreve should check their deployments.