File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path
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 is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.7, `POST /api/share/<path>` accepts an authenticated request for an arbitrary path and stores a public share record without checking whether the target file currently exists. Later, when a file is created at that same path, the previously created public share immediately becomes valid and exposes the new file through `GET /api/public/dl/<hash>`. This vulnerability is fixed in 2.63.7.
From the CVE record · GitHub_M
Before 2.63.7, filebrowser lets an authenticated user create a public share for a path even when no file exists there. If a file is later created at that path, the share becomes valid and exposes the file through a public download endpoint.
Check installations using Go package github.com/filebrowser/filebrowser/v2 before 2.63.7 or github.com/filebrowser/filebrowser at any version through 1.11.0.