In this course,
we've only been able to scratch the surface of sqlmap's functionality.
I use it on almost every engagement, and I'm still learning new tricks.
It's easy to add new payloads to sqlmap, as well as modifying existing ones.
This can be necessary when trying to exploit
vulnerabilities in complicated places.
Another area that we didn't cover that you will run into is
the issue of web application firewalls.
Sqlmap doesn't perform any obfuscation on the payloads it sends.
You can use sqlmap's tamper option to perform obfuscation or
other transformations on your payloads.
Sqlmap has a list of common obfuscation techniques built in,
but it's also very easy to create your own tamper scripts.
This can be helpful in bypassing web application firewalls or other
custom input validation routines that might be in place.
For out‑of‑band data exfiltration,
you can use sqlmap's built‑in DNS capabilities.
For scripting and automation, sqlmap also provides a RESTful Web API.
We gained our initial server access through a web shell.
While this works for initial access, you'll want something more robust.
To this end, sqlmap also supports Metasploit integration.
This means that when exploiting a SQL injection,
instead of a web shell, you can go right to a Metasploit session.
Sqlmap is open source and written in Python.
If you're interested in working on new features or adding additional features,
check out the FAQ to get started.
Also on the Wiki is one of my most referred to resources. The Usage
Wiki page lists all the command line options,
along with a detailed explanation of each.
I hope you leave this course with enough information to start
using sqlmap as part of your tool chain.
Thank you for watching Pluralsight.
I hope you join me and other authors to add to your
arsenal of red team tools in the future.