dice-group / dice-group/Basilisk_old
Security Issue in Basilisk.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Currently, Basilisk secures the benchmark by setting the admin account while running the Basilisk application. Please implement the below two.
1. Restrict the user to provide a strong password, like the minimum number of characters, a combination of lower and upper case and numbers, etc.
2. In the front end and REST API provided by the spring application, When the username and password are taken from the user, there are possibilities of some injection attack, since no sanitizers are used on username and password. Please sanitize the username and password, when you take username and password both in Front end and also in the Spring application.
Thanks,
Ranjith K
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the admin-account setup, the frontend username and password inputs, and the Spring REST endpoints that receive them. Establish the required password rules and the expected safe handling for both inputs, then verify that the frontend and API enforce those requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring
- Domain
- api, authentication, frontend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100