The Mole is an automatic SQL Injection tool for SQLi exploitation for Windows and Linux. Only by providing a vulnerable URL and a valid string on the site it can detect the injection and exploit it, either by using the union technique or a boolean query based technique.
What is The Mole SQL Injection Tool for Windows & Linux?
The Mole uses a command based interface, allowing the user to indicate the action he wants to perform easily. The CLI also provides auto-completion on both commands and command arguments, making the user type as less as possible.
This application is able to exploit both union-based and blind boolean-based injections.
Every action The Mole can execute is triggered by a specific command. All this application requires in order to exploit a SQL Injection is the URL(including the parameters) and a needle(a string) that appears in the server’s response whenever the injection parameter generates a valid query, and does not appear otherwise.
So far, The Mole supports MySQL, MS-SQL and PostgreSQL, but we expect to include other DBMSs in the future.
Features of The Mole SQL Injection Tool
- Support for Mysql, Postgres, SQL Server and Oracle.
- Automatic SQL injection exploitation using union technique.
- Automatic blind SQL injection exploitation.
- Exploits SQL Injections in GET/POST/Cookie parameters.
- Support for filters, in order to bypass certain IPS/IDS rules using generic filters, and the possibility of creating new ones easily.
- Exploits SQL Injections that return binary data.
- Powerful command interpreter to simplify its usage.
Using The Mole SQL Injection Software
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 |
- url [URL [PARAM]]: Gets/sets the URL. If PARAM is given then the injection will be performed on that argument. This can also be provided as an argument to the application, using the "-u" parameter. - needle [NEEDLE]: Gets/sets the NEEDLE. This can also be provided as an argument to the application, using the "-n" parameter. - method (GET|POST <param_post> ) [vulnerable_param]: Sets the method of the request to GET or POST. In case POST is given the param_post string will be used as the POST parameters. If vulnerable_param is given then the mole will use this parameter to inject. - vulnerable_param [<GET|POST|Cookie> VULNERABLE_PARAM]: Sets/gets the type and name of the vulnerable parameter to be exploited by The Mole. - injectable_field [<FIELD_NUM>]: Sets/gets the field of the query which will be used to print the information retrieved when using a union technique. - auth [<basic> <USERNAME:PASSWORD>]: Sets/gets the authentication information used by The Mole in each request. - follow_redirects [<on|off>]: Sets/gets the follow redirect flag. If enabled, The Mole will follow http redirects received from the server. - dbinfo: Fetch current user name, database name and DBMS version. - usercreds: Fetches the credentials for the dbms. Usually requires administrator privileges on the database. - schemas: Fetches the schemas(databases) from the server. The results obtained will be cached, so further calls to this command will return the cached entries. See "fetch" command. - tables <SCHEMA>: Fetches the tables for the schema SCHEMA. The results obtained will be cached, so further calls to this command will return the cached entries. See "fetch" command. e.g: "tables mysql" - columns <SCHEMA> <TABLE>: Fetches the columns for the table TABLE, in the schema SCHEMA. The results obtained will be cached, so further calls to this command will return the cached entries. See "fetch" command. e.g: "columns mysql user" - recursive (schemas|tables <SCHEMA>): Recursively fetches the structure of all schemas or just of the SCHEMA if used with tables. - query <SCHEMA> <TABLE> COLUMN1[,COLUMN2[,COLUMN3[...]]] [where COND]: Perform a query to fetch every column given, using the table TABLE located in the schema SCHEMA. A "where condition" can be given. Note that The Mole will take care of any string conversions required on the condition. Therefore, you can use string literals(using single quotes) even if the server escapes them. Note that no caching is performed when executing this command. e.g: query mysql user User,Password where User = 'root' - fetch <schemas|tables|columns> [args]: This command calls schemas, tables or columns commands depending on the arguments given, forcing them to refetch entries, even if they have already been dumped. This is useful when, after having stopped a query in the middle of it, you want to fetch all of the results and not just those that you were able to dump before stopping it. e.g: "fetch columns mysql user" - readfile <FILE>: Read the FILE from the remote server (if possible) and print it. - find_tables <SCHEMA> <TABLE1> [<TABLE2>, ...]: Bruteforce to find if the TABLES given as parameters are part of the SCHEMA. Useful for MySQL version 4 where no information_schema available. - find_tables_like <SCHEMA> <FILTER>: Perform a query to extract all tables from SCHEMA that match the LIKE filter given as param FILTER. - find_users_table <SCHEMA>: Bruteforce to find tables in SCHEMA that match common names for tables where usernames are stored. - cookie [COOKIE]: Gets/sets a cookie to be sent in each HTTP request's headers. - mode <union|blind>: Sets the SQL Injection exploitation method. By default, union mode is used. If the injection cannot be exploited using this mode, change it to blind using "mode blind" and try again. Nothing else has to be configured to go from union to blind mode, as long as you have already set the URL and needle. - prefix [PREFIX]: Gets/sets the prefix for each request. The prefix will be appended to the URL's vulnerable parameter on each request. - suffix [SUFFIX]: Gets/sets the suffix for each request. The suffix will be appended after the injection code on the URL's vulnerable parameter. - verbose <on|off>: Sets the verbose mode on and off. When this mode is on, each request's parameters will be printed out. - output <pretty|plain>: Sets the output style. When pretty output mode is enabled(this is the default), queries result will be printed on a tidy box, using column names and each row will be aligned. The drawback is that this method requires the whole query to finish before printing results, so you might want to use "plain" output if you seek immediate results. In contrast, plain mode prints each result as soon as it is recovered. e.g: Pretty output might print results like this: +-----------------------------------------------------+ | User | Password | +-----------------------------------------------------+ | blabla | *2B0DDEE3597240B595689260B53D411F515B806D | | foobar | *641B2485F1789F7A6BEE986648B83A899D96793B | +-----------------------------------------------------+ While plain output will print them like this: User, Password: blabla, *2B0DDEE3597240B595689260B53D411F515B806D foobar, *641B2485F1789F7A6BEE986648B83A899D96793B - delay [DELAY]: Gets/Sets the delay between requests. Use this if the server contains some kind of IPS system that returns HTTP error when executing lots of requests in a short amount of time. Note that DELAY can be a floating point number, so you can set "0.5" as the delay. - headers <set|del> <HEADER> [VALUE]: Sets/removes the given HTTP header. Use this to set the User-Agent, cookie, or whatever additional header you want to send. - encoding [ENCODING]: Gets/sets the encoding use to decode the response received. - requestsender [<httpsender|headsender>]: Gets/sets the request sending mechanism. httpsender is the default mechanism, it makes the request and returns the full body of the response. headsender makes a HEAD request and retrieves the headers of the response as the HTML of the response. - qfilter <add|del|config> <FILTER> [ARGS]: Add/configure/remove query filters. Query filters are applied to each query before appending it to the vulnerable parameter. So far, these can be used to either bypass an IPS/IDS or to apply a filter when SQL Server requires you to change the collation of the retrieved fields. - responsefilter <add|del|config> <FILTER> [ARGS]: Adds/removes/configs a response filter. Response filters are applied to the response retrieved from the server. In some cases, invalid HTML can make The Mole miss the injection, so you might want to use a regular expression in order to fix it. - requestfilter <add|del|config> <FILTER> [ARGS]: Add/configure/remove a request filter. Request filters are applied once the request is generated but before it is sent to the server. - export <TYPE> [<ARG1>, ...]: Exports the current mole configuration and the dumped schema's structures for later usage. Currently supported types and params: + xml <FILE>: exports the configuration to an xml file. - import <TYPE> [<ARG1>, ...]: Imports a previously exported mole configuration and dumped schema's structures. Currently supported types and params: + xml <FILE>: imports the configuration from an xml file. - usage <COMMAND>: Print the usage for the command COMMAND. - exit: Exit The Mole. |
Other automated SQLInjection Tools would be:
– BSQL Hacker Download – Automated SQL Injection Tool
– Havij Download – Advanced Automated SQL Injection Tool
– sqlmap – Automated Blind SQL Injection Tool
You can download The Mole SQL Inection Tool here:
Windows: themole-0.3-win32.zip
Linux: themole-0.3-lin-src.tar.gz
Or read more here.