SQL Injection
Also called SQLi.
Injecting SQL through input to manipulate a database query.
What it is
An injection vulnerability where untrusted input alters the structure of a SQL statement sent to a database. Variants include error-based, union-based, and blind (boolean or time-based) techniques for extracting data.
Why it matters
SQL injection can read or modify entire databases and is a perennial cause of large data breaches. Parameterized queries prevent it, and its presence in logs is a high-value detection signal.
In practice
A login field with a crafted apostrophe and OR clause returns all rows, bypassing authentication or dumping the user table.
What to look for
- Quotes, comments and UNION in parameters.
- Database errors returned to users.
- Slow responses that suggest time based tests.
Common mistake
Sanitizing input instead of using parameterized queries. Parameters fix it properly.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Command Injection: Injecting attacker commands into a shell call the app builds.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- Insecure Direct Object Reference: Accessing others' objects by changing an identifier in a request.