dubey/WebGoat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typo (#909)

Browse Source
This commit is contained in:
Gabriel M. Schuyler
2020-12-03 07:23:23 -06:00
committed by GitHub
parent 69c19d19d4
commit b1495a8cd5
6 changed files with 13 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
webgoat-lessons/sql-injection/src/main/resources/lessonPlans/en/SqlInjection_content6c.adoc
View File

@ -1,7 +1,7 @@
== Blind SQL injection
Blind SQL injection is a type of SQL injection attack that asks the database true or false
questions and determines the answer based on the applications response. This attack is often used when the web
questions and determines the answer based on the application's response. This attack is often used when the web
application is configured to show generic error messages, but has not mitigated the code that is vulnerable to SQL
injection.

6
webgoat-lessons/sql-injection/src/main/resources/lessonPlans/en/SqlInjection_introduction_content5_before.adoc
View File

@ -1,6 +1,6 @@
== What is SQL injection?
SQL injections are the most common web hacking techniques. *A SQL injection attack consists of insertion or "injection" of malicious code via the SQL query input from the client to the application.* If not dealt with correctly, such an injection of code into the application can have an serious impact on e.g. data integrity and security.
SQL injections are the most common web hacking techniques. *A SQL injection attack consists of insertion or "injection" of malicious code via the SQL query input from the client to the application.* If not dealt with correctly, such an injection of code into the application can have a serious impact on e.g. data integrity and security.
SQL injections can occur, when unfiltered data from the client, e.g. the input of a search field, gets into the SQL interpreter of the application itself. If the input from the client does not get checked for containing SQL commands, hackers can easily manipulate the underlying SQL statement to their advantage. +
Per example if the input is not filtered for SQL metacharacters like *--* (comments out the rest of the line) or *;* (ends a SQL query and that way can be used to chain them).
@ -11,7 +11,7 @@ Per example if the input is not filtered for SQL metacharacters like *--* (comme
Think of a web application, that allows to display user information, by typing a username into an input field.
The input will then be sent to the server and gets inserted into a SQL query which then is processed by an SQL interpreter.
The input will then be sent to the server and gets inserted into a SQL query which then is processed by a SQL interpreter.
The SQL query to retrieve the user information from the database looks like that: +
-------------------------------------------------------
@ -28,4 +28,4 @@ and would retrieve all data for the user with the name Smith.
{nbsp} +
But if an attacker supplies an unexpected input which could be part of a SQL query, the query itself can be modified and that way be used to perform other (malicious) actions on the database.
Here is an input field. Try typing some SQL in here to better understand how the query changes.
Here is an input field. Try typing some SQL in here to better understand how the query changes.