RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution
rclone
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rclone/rclone Go |
|
|
| github.com/ncw/rclone Go |
| No fix yet |
rclone
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rclone/rclone Go |
|
|
| github.com/ncw/rclone Go |
| No fix yet |
Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Starting in version 1.48.0 and prior to version 1.73.5, the RC endpoint `operations/fsinfo` is exposed without `AuthRequired: true` and accepts attacker-controlled `fs` input. Because `rc.GetFs(...)` supports inline backend definitions, an unauthenticated attacker can instantiate an attacker-controlled backend on demand. For the WebDAV backend, `bearer_token_command` is executed during backend initialization, making single-request unauthenticated local command execution possible on reachable RC deployments without global HTTP authentication. Version 1.73.5 patches the issue.
From the CVE record · GitHub_M
The RC operations/fsinfo endpoint accepts attacker-controlled backend definitions without requiring authentication. On reachable RC deployments without global HTTP authentication, an unauthenticated attacker can trigger local command execution through WebDAV backend initialization with a single request.
Check deployments using github.com/rclone/rclone versions 1.48.0 to before 1.73.5, or github.com/ncw/rclone versions 1.48.0 and later.