Update SQL Injection Web security documentation to the best practices. #37806
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -81,18 +81,21 @@ SELECT * FROM users WHERE name = 'a';DROP TABLE users; SELECT * FROM userinfo WH | |||
|
|
|||
| The modified statement creates a valid SQL statement that deletes the `users` table and selects all data from the `userinfo` table (which reveals the information of every user). This works because the first part of the injected text (`a';`) completes the original statement. | |||
|
|
|||
| To avoid this sort of attack, you must ensure that any user data that is passed to an SQL query cannot change the nature of the query. One way to do this is to [escape](https://en.wikipedia.org/wiki/Escape_character) all the characters in the user input that have a special meaning in SQL. | |||
| To avoid such attacks, the best practice is to use *parameterized queries* (prepared statements). This approach ensures that the user input is treated as a string of data rather than executable SQL. | |||
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
| To avoid such attacks, the best practice is to use *parameterized queries* (prepared statements). This approach ensures that the user input is treated as a string of data rather than executable SQL. | |
| To avoid such attacks, the best practice is to use _parameterized queries_ (prepared statements). This approach ensures that the user input is treated as a string of data rather than executable SQL. |
|
|
||
| In the following statement, we escape the **'** character. The SQL will now interpret the name as the whole string in bold (which is a very odd name indeed, but not harmful). | ||
| ````SQL |
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
| ````SQL | |
| ```SQL |
| In the following statement, we escape the **'** character. The SQL will now interpret the name as the whole string in bold (which is a very odd name indeed, but not harmful). | ||
| ````SQL | ||
| SELECT * FROM users WHERE name = ? AND password = ?; | ||
| ```` |
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
| ```` | |
| ``` |
| ``` | ||
| When executing the above query, for example, in Python, we pass the `name` and `password` as parameters, as shown below. | ||
|
|
||
| ````Python |
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
| ````Python | |
| ```Python |
|
|
||
| ````Python | ||
| cursor.execute("SELECT * FROM users WHERE name = ? AND password = ?", (name, password)) | ||
| ```` |
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
| ```` | |
| ``` |
|
Preview URLs (comment last updated: 2025-01-27 17:47:11) |
Np |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated SQL Injection Web security documentation to the best practices.
Motivation
These changes ensure that developers are aware of the standard and best practices related to sql injection.
Additional details
None
Related issues and pull requests
Fixes #37783