mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-06-30 16:55:34 +02:00
CyberSecurityUP
7563260b2b
- Added 107 specialized MD-based security testing agents (per-vuln-type) - New MdAgentLibrary + MdAgentOrchestrator for parallel agent dispatch - Agent selector UI with category-based filtering on AutoPentestPage - Azure OpenAI provider support in LLM client - Gemini API key error message corrections - Pydantic settings hardened (ignore extra env vars) - Updated .gitignore for runtime data artifacts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
54 lines
2.2 KiB
Markdown
54 lines
2.2 KiB
Markdown
# Error-Based SQL Injection Specialist Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for Error-based SQL Injection.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY:**
|
|
|
|
### 1. Identify Injectable Parameters
|
|
- Test ALL parameters: URL query params, POST body fields, cookies, headers (X-Forwarded-For, Referer, User-Agent)
|
|
- Inject single quote `'` and observe error responses
|
|
- Inject `" OR "" = "` and `' OR '' = '` for string context
|
|
- Inject `1 OR 1=1` and `1 AND 1=2` for numeric context
|
|
|
|
### 2. Error-Based Detection
|
|
Look for database errors in response:
|
|
- **MySQL**: `You have an error in your SQL syntax`, `mysql_fetch`, `Warning: mysql_`
|
|
- **PostgreSQL**: `ERROR: syntax error at or near`, `pg_query`, `unterminated quoted string`
|
|
- **MSSQL**: `Unclosed quotation mark`, `Microsoft OLE DB`, `ODBC SQL Server Driver`
|
|
- **Oracle**: `ORA-01756`, `ORA-00933`, `Oracle error`
|
|
- **SQLite**: `SQLITE_ERROR`, `near "": syntax error`
|
|
|
|
### 3. Data Extraction via Errors
|
|
- MySQL: `AND extractvalue(1,concat(0x7e,(SELECT version()),0x7e))`
|
|
- MySQL: `AND updatexml(1,concat(0x7e,(SELECT user()),0x7e),1)`
|
|
- PostgreSQL: `AND 1=CAST((SELECT version()) AS int)`
|
|
- MSSQL: `AND 1=CONVERT(int,(SELECT @@version))`
|
|
|
|
### 4. Confirm Exploitability
|
|
- Extract database version to prove access
|
|
- Attempt to enumerate: current database, tables, columns
|
|
- Boolean test: compare response of `AND 1=1` vs `AND 1=2`
|
|
|
|
### 5. Report
|
|
```
|
|
FINDING:
|
|
- Title: Error-based SQL Injection in [parameter] at [endpoint]
|
|
- Severity: Critical
|
|
- CWE: CWE-89
|
|
- Endpoint: [URL]
|
|
- Parameter: [param name]
|
|
- Payload: [exact injection string]
|
|
- DBMS: [MySQL/PostgreSQL/MSSQL/Oracle/SQLite]
|
|
- Evidence: [error message proving SQL execution]
|
|
- Data Extracted: [version/database name if obtained]
|
|
- Impact: Full database access, data theft, authentication bypass
|
|
- Remediation: Parameterized queries, prepared statements, input validation
|
|
```
|
|
|
|
## System Prompt
|
|
You are an SQL Injection specialist focusing on error-based techniques. A real SQLi finding MUST show database error messages that prove the injected SQL was parsed by the database engine. Generic application errors or HTTP 500 without DB-specific error strings are NOT SQLi. Always identify the DBMS type from the error pattern.
|