In-app reader
An attacker can completely bypass file-name randomization security and without authorization download confidential, signed EULA files belonging to any other user across the application.
Log in as a restricted user.
Send a GET request to /api/v1/users/{target_id}/eulas (where target_id belongs to a restricted/denied user).
Observe the response leaks the secret EULA filename (e.g., eula-xxx.pdf).
Attempt to access this file via the main route: GET /stored-eula-file/{filename} (This will correctly return 403 Forbidden).
Now, access the file via the vulnerable profile route: GET /account/stored-eula-file/{filename}.
Observe that the server returns a 200 OK and successfully downloads the target user's secret EULA file.
Fixed in grokability/snipe-it@f15d786
Discussion
Sign in to join the discussion.
Keep reading
Optional: create a free account to save items, track programs, and sync across web + app. Reading stays free.