Tool Tuesday – sqlmap
Is your web application vulnerable to SQL Injection? With sqlmap you can test it.
First things first: A SQL Injection is a vulnerability in a web application that allows SQL commands to be sent to the database because the web application has not implemented appropriate countermeasures. More information can be found at: https://www.owasp.org/index.php/SQL_Injection. If you find evidence of such a vulnerability, you can use sqlmap to accurately verify the vulnerability.
sqlmap is a commandline tool for automated checking for SQL injections. This tool provides a wealth of options. sqlmap uses all known techniques to detect SQL injection, like Boolean-based, Time-based, Error-based, UNION-based and Stacked queries. The aggression with which sqlmap proceeds can also be set to control the impact on network traffic.
If a vulnerability is detected, sqlmap can also be used to exploit this vulnerability. The tool is able to detect the used database systems, extract single tables or create an dump of the complete database. In some cases it is also possible to get a shell to the operating system of the database server.
More information can be found at: http://sqlmap.org/
Are you not sure whether SQL Injections are possible in your application? Please feel free to contact us!
How can you actively prevent usernames from being enumerated on WordPress author pages?
In our Big Application Security Penetration Test FAQ for clients we answer everything you should know before, during and after the commissioning of an Application Security Penetration Test.
In focus today: Questions #18 and #19 – How are vulnerabilities found evaluated? And what is the CVSS?
CSRF Countermeasures #2: Another way to protect against CSRF – stateless – is the Double Submit Cookie method.
The NinjaDVA is our comfortable and flexible training environment.
CSRF Countermeasures #1: One possibility to prevent CSRF is the usage of an anti-CSRF token.