{"id":1958,"date":"2009-07-31T10:42:55","date_gmt":"2009-07-31T10:42:55","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=1958"},"modified":"2015-09-09T19:37:58","modified_gmt":"2015-09-09T11:37:58","slug":"sqlmap-0-7-released-automatic-sql-injection-tool","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2009\/07\/sqlmap-0-7-released-automatic-sql-injection-tool\/","title":{"rendered":"sqlmap 0.7 Released – Automatic SQL Injection Tool"},"content":{"rendered":"

[ad]<\/p>\n

We’ve been following sqlmap since it first came out in Feburary 2007<\/a> and it’s been quite some time since the last update sqlmap 0.6.3 in December 2008<\/a>. <\/p>\n

For those not familiar with the tool, sqlmap is an open source command-line automatic SQL injection tool. Its goal is to detect and take advantage of SQL injection vulnerabilities in web applications.<\/p>\n

Once it detects one or more SQL injections on the target host, the user can choose among a variety of options to perform an extensive back-end database management system fingerprint, retrieve DBMS session user and database, enumerate users, password hashes, privileges, databases, dump entire or user’s specified DBMS tables\/columns, run his own SQL statement, read or write either text or binary files on the file system, execute arbitrary commands on the operating system, establish an out-of-band stateful connection between the attacker box and the database server via Metasploit payload stager, database stored procedure buffer overflow exploitation or SMB relay attack and more.<\/p>\n

Recent Changes<\/strong><\/p>\n

Along all the takeover features introduced in sqlmap 0.7 release candidate 1, some of the new features include:<\/p>\n