File Browser allows sensitive data to be transferred in URL
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. Prior to version 2.33.9, access tokens are used as GET parameters. The JSON Web Token (JWT) which is used as a session identifier will get leaked to anyone having access to the URLs accessed by the user. This will give an attacker full access to a user's account and, in consequence, to all sensitive files the user has access to. This issue has been patched in version 2.33.9.
From the CVE record · GitHub_M
Before version 2.33.9, filebrowser puts session JWTs in URL query parameters. Anyone who can access a user's visited URLs can obtain the token and gain full access to that user's account and accessible files.
Operators using Go package github.com/filebrowser/filebrowser/v2 before 2.33.9 or github.com/filebrowser/filebrowser through 1.11.0 should check their installations.