mirror of
https://github.com/xalgord/My-Methodologies.git
synced 2024-11-10 06:04:20 +00:00
GITBOOK-74: change request with no subject merged in GitBook
This commit is contained in:
parent
67e35f6c14
commit
f744fea5a6
2 changed files with 8 additions and 2 deletions
|
@ -19,6 +19,6 @@
|
||||||
* [🔎 Recon Like a Boss](recon-strategies-by-other-hackers/recon-like-a-boss.md)
|
* [🔎 Recon Like a Boss](recon-strategies-by-other-hackers/recon-like-a-boss.md)
|
||||||
* [🔎 Recon With Me](recon-strategies-by-other-hackers/recon-with-me.md)
|
* [🔎 Recon With Me](recon-strategies-by-other-hackers/recon-with-me.md)
|
||||||
* [🔎 Simple Recon Methodology](recon-strategies-by-other-hackers/simple-recon-methodology.md)
|
* [🔎 Simple Recon Methodology](recon-strategies-by-other-hackers/simple-recon-methodology.md)
|
||||||
* [SQL injection through HTTP headers](recon-strategies-by-other-hackers/sql-injection-through-http-headers.md)
|
* [🔎 SQL injection through HTTP headers](recon-strategies-by-other-hackers/sql-injection-through-http-headers.md)
|
||||||
* [🎯 subdomain-enumeration](subdomain-enumeration/README.md)
|
* [🎯 subdomain-enumeration](subdomain-enumeration/README.md)
|
||||||
* [❌ xss](xss/README.md)
|
* [❌ xss](xss/README.md)
|
||||||
|
|
|
@ -1,4 +1,10 @@
|
||||||
# SQL injection through HTTP headers
|
---
|
||||||
|
description: >-
|
||||||
|
source:
|
||||||
|
https://resources.infosecinstitute.com/topics/application-security/sql-injection-http-headers/
|
||||||
|
---
|
||||||
|
|
||||||
|
# 🔎 SQL injection through HTTP headers
|
||||||
|
|
||||||
During vulnerability assessment or penetration testing, identifying the input vectors of the target application is a primordial step. Sometimes, when dealing with Web application testing, verification routines related to [SQL injection](https://www.infosecinstitute.com/skills/courses/sql-injection/?utm\_source=resources\&utm\_medium=infosec+network\&utm\_campaign=skills+pricing\&utm\_content=hyperlink) flaws discovery are restricted to the GET and POST variables as the unique inputs vectors ever.
|
During vulnerability assessment or penetration testing, identifying the input vectors of the target application is a primordial step. Sometimes, when dealing with Web application testing, verification routines related to [SQL injection](https://www.infosecinstitute.com/skills/courses/sql-injection/?utm\_source=resources\&utm\_medium=infosec+network\&utm\_campaign=skills+pricing\&utm\_content=hyperlink) flaws discovery are restricted to the GET and POST variables as the unique inputs vectors ever.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue