When successful, the attack allows the attacker to inject data into an existing SQL query. The attacker may then be able to fetch private data, cause a denial of service or cause other unintended responses. In the worst case, the injected code would allow the attacker to gain full control of the system by exploiting multiple vulnerabilities in the database server, system utilities and operating system.
For an overview of SQL injection attacks, review Wikipedia's SQL Injection page.
The following code snippet would allow an attacker to execute their own SQL commands (and is a syntax error in Oracle).
$limit = $wgRequest->getVal( 'limit' ); $res = $db->query( "SELECT * from kitties LIMIT $limit" );
The preferred way to run the above query would be:
$limit = $wgRequest->getVal( 'limit' ); $limit = intval( $limit ); // OPTIONAL validation $res = $db->select( 'kitties', '*', false, __METHOD__, array( 'LIMIT' => $limit ) // REQUIRED automatic escaping );
To exploit the vulnerability and fetch the email addresses of registered wiki users, the attacker would use a GET string of:
SQL Injection and MediaWikiEdit
MediaWiki has a custom SQL generation interface which has proven to be effective for eliminating SQL injection vulnerabilities. The SQL generation interface also provides DBMS abstraction and features such as table prefixes.
To keep MediaWiki safe from SQL injection
- avoid using direct SQL queries at all costs;
- review Manual:Database access and use the functions provided in Database.php; and
- read the The Open Web Application Security Project's page on SQL injection (http://www.owasp.org/index.php/SQL_Injection).
- The SQL Injection Wiki: http://www.sqlinjectionwiki.com/