Summary
In the web application, 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.
Impact
Shell commands are executed with the uid of the server process without any further restrictions.
This means, that they will have access to at least
- all files managed by the application from all scopes, even those the user does not have access to in the GUI.
- the Filebrowser database file containing the password hashes of all accounts.
The concrete impact depends on the commands being granted to the attacker, but due to other vulnerabilities identified ("Bypass Command Execution Allowlist", "Shell Commands Can Spawn Other Commands", "Insecure File Permissions") it is likely, that full read- and write-access will exist.
Read access to the database means, that the attacker is capable of extracting all user password hashes.
This enables an offline dictionary attack on the passwords of all accounts, though the choice of the password hash function (bcrypt with a complexity of 10) gives a strong protection against such attacks.
Write access to the database means that attackers are capable of changing a user's password hash, allowing them to impersonate any user account, including an administrator.
Vulnerability Description
Shell commands executed by a user are created as a simple subprocess of the application without any further restrictions.
That means, that they have full access to files accessible by the application.
The scope that is assigned to every account is not considered.
As a prerequisite, an attacker needs an account with the Execute Commands permission and some permitted commands.
Proof of Concept
Any exploit highly depends on the commands granted to the attacker.
The following screenshot shows, how all password hashes can be extracted using only the grep command:
Recommended Countermeasures
Until this issue is fixed, we 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.
As a defense-in-depth measure, organizations not requiring command execution should operate the Filebrowser from a distroless container image.
There are two approaches to fixing this issue:
- Limiting the process when it is started e.g., by using user namespaces with a tool like Bubblewrap. If this path is chosen, it is important to use a method that works both on a bare-metal server and within an unprivileged container.
- Re-architecting the command execution feature so that file in the various scopes have a distinct uid as an owner and all shell command are executed under the uid of the user's scope.
Timeline
2025-03-26 Identified the vulnerability in version 2.32.02025-04-11 Contacted the project2025-04-18 Vulnerability disclosed to the project2025-06-25 Uploaded advisories to the project's GitHub repository2025-06-25 CVE ID assigned by GitHub2025-06-25 A patch version has been pushed to disable the feature for all existent installations, and making it opt-in. A warning has been added to the documentation and is printed on the console if the feature is enabled. Due to the project being in maintenance-only mode, the bug has not been fixed. Fix is tracked on filebrowser/filebrowser#5199.
References
Credits
References
Summary
In the web application, 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.
Impact
Shell commands are executed with the uid of the server process without any further restrictions.
This means, that they will have access to at least
The concrete impact depends on the commands being granted to the attacker, but due to other vulnerabilities identified ("Bypass Command Execution Allowlist", "Shell Commands Can Spawn Other Commands", "Insecure File Permissions") it is likely, that full read- and write-access will exist.
Read access to the database means, that the attacker is capable of extracting all user password hashes.
This enables an offline dictionary attack on the passwords of all accounts, though the choice of the password hash function (bcrypt with a complexity of 10) gives a strong protection against such attacks.
Write access to the database means that attackers are capable of changing a user's password hash, allowing them to impersonate any user account, including an administrator.
Vulnerability Description
Shell commands executed by a user are created as a simple subprocess of the application without any further restrictions.
That means, that they have full access to files accessible by the application.
The scope that is assigned to every account is not considered.
As a prerequisite, an attacker needs an account with the
Execute Commandspermission and some permitted commands.Proof of Concept
Any exploit highly depends on the commands granted to the attacker.
The following screenshot shows, how all password hashes can be extracted using only the
grepcommand:Recommended Countermeasures
Until this issue is fixed, we recommend to completely disable
Execute commandsfor 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.
As a defense-in-depth measure, organizations not requiring command execution should operate the Filebrowser from a distroless container image.
There are two approaches to fixing this issue:
Timeline
2025-03-26Identified the vulnerability in version 2.32.02025-04-11Contacted the project2025-04-18Vulnerability disclosed to the project2025-06-25Uploaded advisories to the project's GitHub repository2025-06-25CVE ID assigned by GitHub2025-06-25A patch version has been pushed to disable the feature for all existent installations, and making it opt-in. A warning has been added to the documentation and is printed on the console if the feature is enabled. Due to the project being in maintenance-only mode, the bug has not been fixed. Fix is tracked on filebrowser/filebrowser#5199.References
Credits
References