Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL Injection priorities #92

Closed
truemongo opened this issue Sep 21, 2017 · 2 comments · Fixed by #96
Closed

SQL Injection priorities #92

truemongo opened this issue Sep 21, 2017 · 2 comments · Fixed by #96

Comments

@truemongo
Copy link

Noticed the top-level "SQL Injection" does not have a priority set, while the 2 subcategories (Blind and Error-based) are both P1.
Should probably either set P1 on the top-level category or add a new subcategory for SQL injection when attacker can get output directly.
If going with the 2nd option, not sure what you'd call it, maybe "SQL Injection - UNION Based"?

@plr0man
Copy link
Contributor

plr0man commented Oct 4, 2017

Hi @truemongo, sorry for the long wait. After consulting with the team we have decided to remove the SQLi subcategories and leave the SQLi category as a P1 entry with no children. Let me know if you see any arguments against doing so.

@plr0man plr0man added this to the v1.4 milestone Oct 4, 2017
@truemongo
Copy link
Author

No problem, and that sounds good to me! Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants