From 592b45106b44cb3e0ee545f3becea336631119a4 Mon Sep 17 00:00:00 2001 From: whx Date: Mon, 14 Nov 2022 00:58:35 +0100 Subject: [PATCH] typos --- Exploits/Databases/SQL Injection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Exploits/Databases/SQL Injection.md b/Exploits/Databases/SQL Injection.md index a3b90c3..679765f 100644 --- a/Exploits/Databases/SQL Injection.md +++ b/Exploits/Databases/SQL Injection.md @@ -1,6 +1,6 @@ # SQL Injection -In an SQL injection an SQL command is ended prematurely through setting the quote earlier than intended by the original programmer. The malicious command is then ended by an SQL comment to ignore the following parts of the original SQL command. +In an SQL injection an SQL statement is ended prematurely through setting the quote earlier than intended by the original programmer. The malicious command is then ended by an SQL comment to ignore the following parts of the original SQL statement. A piece of understanding the way of injecting malicious SQL commands is to understand the syntax of [MySQL Comments](https://blog.raw.pm/en/sql-injection-mysql-comment/). * [OWASP SQLi Docs](https://www.owasp.org/index.php/SQL_Injection) @@ -72,7 +72,7 @@ http://example.com/?id=1' and (ascii(substr((select database(),1,1)) = 115 --+ Union based injections is an incremental and cautios approach. Start by trying to provoke errors to validate a possible injection. -* _First method__ check by order until error occurs +* __First method__ check by order until error occurs ```sql ' order by 1 -- - ' order by 2 -- -