Skip to main content

Injection Vulnerabilities

Injection flaws occur when untrusted data is sent to an interpreter as part of a command or query. AIPTx comprehensively tests for all common injection types.

SQL Injection

Types Detected

Testing Approach

AIPTx tests SQL injection by:
  1. Parameter Discovery - Identifying all injectable parameters
  2. Database Fingerprinting - Detecting database type (MySQL, PostgreSQL, MSSQL, Oracle)
  3. Payload Generation - Context-aware payloads for each database
  4. Exploitation - Validating with data extraction attempts

Example Finding

NoSQL Injection

Databases Covered

  • MongoDB
  • CouchDB
  • Redis
  • Cassandra
  • DynamoDB

Attack Vectors

Testing Methodology

  1. Identify NoSQL endpoints
  2. Test operator injection ($ne, $gt, $lt, $regex)
  3. Test JavaScript injection in $where clauses
  4. Test array/object manipulation

Command Injection

OS Command Injection

AIPTx tests for command injection in:
  • File operations
  • System utilities
  • Shell commands
  • Process execution

Payloads

Example Finding

LDAP Injection

Testing Coverage

  • Authentication bypass
  • Information disclosure
  • Filter manipulation

Payloads

Template Injection (SSTI)

Supported Frameworks

Exploitation Chain

  1. Detection - Identify template engine
  2. Context - Determine injection context
  3. Sandbox Escape - Test for RCE capability
  4. Exploitation - Execute arbitrary code

XPath Injection

Testing Scenarios

Header Injection

Types

  • Host header injection
  • X-Forwarded-For manipulation
  • Email header injection (CRLF)

Example

Remediation Guidance

Prevention:
  • Use parameterized queries / prepared statements
  • Implement input validation
  • Apply least privilege database accounts
Prevention:
  • Avoid shell commands when possible
  • Use allowlists for permitted characters
  • Escape special characters
Prevention:
  • Validate input types
  • Sanitize user input
  • Use query builders with parameterization