False negative related to SQL Injection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 673
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
The endpoint: https://brokencrystals.com/api/testimonials/count?query=%27 is vulnerable to an SQL injection
The endpoint does NOT return 50X error when the SQL injection occurs, thus: STATUS_CODE_FILTER doesn't catch it
I believe it would be a smart idea to look for common SQL errors such as:
' - unterminated quoted string at or near "'"
Other errors are listed here:
https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/07-Input_Validation_Testing/05-Testing_for_SQL_Injection
I can't easily find one 'list' that has all the SQL errors
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior at the testimonials/count endpoint and trace where STATUS_CODE_FILTER handles responses. Review the linked OWASP SQL injection testing guidance and the issue's quoted database error. Done means the false negative is detected through the supported response checks, with coverage for the relevant error responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100