File Browser: Command Execution not Limited to Scope
filebrowser
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/filebrowser/filebrowser/v2 Go |
|
|
| github.com/filebrowser/filebrowser Go |
| No fix yet |
filebrowser
| Product | Affected | Fixed in |
|---|---|---|
| github.com/filebrowser/filebrowser/v2 Go |
|
|
| github.com/filebrowser/filebrowser Go |
| No fix yet |
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. In versions of the web application on the 2.x branch, all users have a scope assigned, and they only have access to the files within that scope. The Command Execution feature of Filebrowser allows the execution of shell commands which are not restricted to the scope, potentially giving an attacker read and write access to all files managed by the server. Until this issue is fixed, the maintainers recommend to completely disable `Execute commands` for all accounts. Since the command execution is an inherently dangerous feature that is not used by all deployments, it should be possible to completely disable it in the application's configuration. This feature has been disabled by default for all installations from v2.33.8 onwards, including for existent installations. To exploit this vulnerability, the instance administrator must turn on a feature and ignore all the warnings about known vulnerabilities.
From the CVE record · GitHub_M
In filebrowser 2.x, shell commands run through Command Execution are not restricted to a user's assigned file scope. A user with access to this feature could read or write files outside their scope, but exploitation requires an administrator to enable the feature despite its vulnerability warnings.
Operators running filebrowser 2.x, including users of Go packages github.com/filebrowser/filebrowser/v2 before 2.33.8 or github.com/filebrowser/filebrowser at any version, should check their installations.