You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before creating a bug report please make sure you are using the latest docker image / code base.
Please complete the following information
Installation Type: [Docker]
Running locally with docker compose file from readme
Have you tried using the latest docker image / code base [yes]
Current Version 2022.07.06
Describe the bug
A vehicle's details can be opened by any logged in user if the url is known. This is an issue when a vehicle was previously shared with a user (so they know the url) but isn't anymore. Having shared the vehicle before is not required for the bug though.
To Reproduce
Steps to reproduce the behavior:
Have at least two users.
Create vehicle with user A.
Do NOT share vehicle with user B.
Remember vehicle url.
Log in with user B.
Open url from step 4.
See all details of not shared vehicle
Expected behavior
User B cannot access vehicles that are owned by user A and not shared with user B
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Without logged-in user, the vehicle url redirects correctly to the login screen.
As user B, adding expenses or fillups fails because the vehicle is not selectable from the dropdown. I haven't tested using any rest api directly, so that might be worth checking.
Let me know if you need more info or logs
The text was updated successfully, but these errors were encountered:
I didn't test, maybe you are right.
Looks there are no checks in place to see if you "own" the resource.
Something like this gin-gonic/gin#2612 , adding a router middleware to block unwanted interaction.
Before creating a bug report please make sure you are using the latest docker image / code base.
Please complete the following information
Describe the bug
A vehicle's details can be opened by any logged in user if the url is known. This is an issue when a vehicle was previously shared with a user (so they know the url) but isn't anymore. Having shared the vehicle before is not required for the bug though.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User B cannot access vehicles that are owned by user A and not shared with user B
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Let me know if you need more info or logs
The text was updated successfully, but these errors were encountered: