We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be great if we have a sanitize() function fo user input tool to prevent SQL injection. Consider this code
{ "anonymousId": some_user_input, "email": "[email protected]" }
if user sends SQL injection some_user_input= "0" or something=1 or anonymousId="0", then the result will be
{ "anonymousId": "0\" or something=1 or anonymousId=\"0", "email": "[email protected]" }
and the error output will contain secure information about all available fields.
empty result as there is no such anonymous id "0" or something=1 or anonymousId="0"
and the output will contain secure information about all available fields.
This is classical SQL injection which possibly appears in every user controller where controller expects user input
Provide sanitize() function which prevent SQL injections
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
It would be great if we have a sanitize() function fo user input tool to prevent SQL injection. Consider this code
if user sends SQL injection some_user_input= "0" or something=1 or anonymousId="0", then the result will be
and the error output will contain secure information about all available fields.
Expected Behavior
empty result as there is no such anonymous id "0" or something=1 or anonymousId="0"
Current Behavior
and the output will contain secure information about all available fields.
Context
This is classical SQL injection which possibly appears in every user controller where controller expects user input
Possible Solution
Provide sanitize() function which prevent SQL injections
The text was updated successfully, but these errors were encountered: