quentinphilipp / bikenweb Goto Github PK

Describe the bug
Our security team is working on the automated detection of session vulnerabilities in opensource web applications, including insecure hashing of authentication credentials. Our analyzer identified that the set_password function of BikenWeb/biken
/models.py is using an unsafe hashing function (SHA-256) to store users' passwords. This practice might leave your application vulnerable to offline bruteforcing attacks.

Can you take a look into the relevant code parts and comment on the issue?

To Reproduce
Upon data breach, an attacker with access to the password database can perform offline bruteforcing to reconstruct valid users' passwords, possibly reused at other services. This can be avoided by using more secure hashing algorithms.

Expected behavior
Please follow the OWASP recommendations for secure password hashing to avoid the issue: https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html

The average speed is 15km/h, it need to be changed to an higher values for road cycling (~30km/h)

Most of the time the route is bigger than what was requested by the user. We need to find a solution to patch this problem.

The routes are created with multiples itinerary linked one to each other. We need to make sure there is no useless road that go to one point and go back just after (u-turn) for nothing.

The inputs for the itineraries and routes are in the navbar so they are accesible from everywhere. Currently if you try to generate an itinerary from page different that the home page it's not working