Описание
filebrowser Sets Insecure File Permissions
Summary
The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account.
Impact
The default permissions for new files on a standard Linux system are 0644, making them world-readable.
That means that at least the following parties have full read access to all files managed by the Filebrowser from all scopes, as well as its database (including the password hashes stored in there):
- All OS accounts on the server
- All other applications running on the same server
- Any Filebrowser user with Command Execution privileges having access to a command that allows reading a file's content
Vulnerability Description
On a Linux system, the file access permissions of new files are designated by the system wide umask setting, unless they are configured manually.
Most distributions set this value to 022 by default which gives every account on the system read permissions on the file.
Proof of Concept
Upload or create a file in the Filebrowser GUI and list the directory contents from a shell:
The same can be validated for Docker based deployments within the container:
Furthermore, the database used by the Filebrowser application is readable by any account:
Recommended Countermeasures
Since the system's umask configuration cannot be controlled by the Filebrowser, the application needs to set the permissions of all new files manually upon creation. No permissions should be given to the other category.
Implementing this won't fix the permissions for active instances after an update, so site administrators will need to fix the permissions manually:
Timeline
2025-03-25Identified 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-26CVE ID assigned by GitHub2025-06-26Fix released with version 2.33.7
References
- CWE-276: Incorrect Default Permissions
- What is Umask and How To Setup Default umask Under Linux?
- Original Advisory
Credits
- Mathias Tausig (SBA Research)
Ссылки
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-jj2r-455p-5gvf
- https://nvd.nist.gov/vuln/detail/CVE-2025-52900
- https://github.com/filebrowser/filebrowser/commit/ca86f916216620365c0f81629c0934ce02574d76
- https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250325-03_Filebrowser_Insecure_File_Permissions
- https://pkg.go.dev/vuln/GO-2025-3785
Пакеты
github.com/filebrowser/filebrowser/v2
< 2.33.7
2.33.7
github.com/filebrowser/filebrowser
<= 1.11.0
Отсутствует
Связанные уязвимости
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers using File Browser prior to version 2.33.7 where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Version 2.33.7 fixes the issue.