Sniper – Automatic Exploiter
We developed Sniper to bridge the gap between results that common vulnerability scanners produce (e.g. Nessus, Qualys, OpenVAS) and the attack methods real threat actors use. While vulnerability scanners generate a high volume of potential issues, which also include a lot of noise and false positives, real attackers commonly focus on a few highly effective and targeted intrusion techniques.
Sniper is a custom tool that implements a set of modules for exploiting the most critical vulnerabilities in high-profile software that the majority of companies in the world use. The tool mimics the exploits and attack techniques found in real world scenarios to determine the truly vulnerable systems.
After a successful exploitation, Sniper automatically runs post-exploitation modules which extract interesting data from the target system as solid proof of intrusion. We call this data artefacts. Here are some artefact examples:
- Current user (e.g.
- System information
- List of local users
- List of running processes
- Network configuration
- Network neighbors
- Network connections
Security teams and specialists can use all this data to continue their pentesting work into the network (manually, by the pentester) and for vulnerability validation.
When Sniper succeeds in exploiting a vulnerability, system administrators must act straight away, as the risk is real and attackers can exploit it at any given moment. This tool helps you become very effective at filtering out the noise that vulnerability scanners create, eliminating false positives, and helping you focus on the vulnerabilities that matter.
This is the complete list of modules and capabilities currently available in Sniper:
|VPN Gateway||F5||BIG IP||May 2022||-||RCE|
|API Management||WSO2||Platform||Apr 2022||-||RCE|
|Web Framework||Apache||Struts||Apr 2022||S2-062||RCE|
|Web framework||Pivotal Software||Spring Framework||Mar 2022||-||RCE|
|Library||Pivotal Software||Spring Cloud Gateway||Mar 2022||-||RCE|
|Data store||Redis||Redis||Feb 2022||-||RCE|
|Monitoring solution||Zabbix||Zabbix||Jan 2022||-||RCE|
|Hypervisor||ManageEngine||Desktop Central||Dec 2021||-||RCE|
|Web Framework||Apache||Struts||Dec 2021||Log4Shell||RCE|
|Logging library||Apache||Log4j||Dec 2021||Log4Shell||RCE|
|Hypervisor||ManageEngine||ServiceDesk, SupportCenter||Nov 2021||-||RCE|
|Monitoring solution||Grafana||Labs||Nov 2021||-||File Read|
|Webserver||Apache||Server||Oct 2021||-||File Read|
|Webserver||Apache||Server||Oct 2021||-||File Read|
|Azure Cloud||Microsoft||Open Management Interface (OMI)||Sep 2021||OMIGOD||RCE|
|Password Management||ManageEngine||ADSelfService Plus||Sep 2021||-||RCE|
|Email Server||Microsoft||Exchange Server||Aug 2021||ProxyShell||RCE|
|Collaboration Software||Atlassian||Confluence||Aug 2021||-||RCE|
|Monitoring System||VisualTools||DVR||Jul 2021||-||RCE|
|Virtualization||VMware||vCenter Server||May 2021||-||RCE|
|Virtualization||VMware||Workspace One||Apr 2021||-||RCE|
|Collaboration Software||GitLab||Server||Apr 2021||-||RCE|
|VPN Gateway||F5||BIG IP||Mar 2021||-||RCE|
|Email Server||Microsoft||Exchange Server||Mar 2021||ProxyLogon||RCE|
|Planning System||Apache||OFBiz||Mar 2021||-||RCE|
|Webserver||Sebastian Hildebrandt||System Information Library for Node.JS||Feb 2021||-||RCE|
|Virtualization||VMware||vCenter Server||Feb 2021||-||RCE|
|Webserver||Node||Red||Jan 2021||-||File Read|
|Web Framework||Laravel||Laravel||Jan 2021||-||RCE|
|Web Framework||Apache||Struts||Dec 2020||-||RCE|
|Web Framework||Oracle||Weblogic||Oct 2020||-||RCE|
|Networking product||Netgear||Router||Oct 2020||-||RCE|
|Firewall||Sophos||SG UTM||Sep 2020||-||RCE|
|Web Framework||Apache||Struts||Aug 2020||-||RCE|
|Firewall||Citrix||ADC/Gateway||Jul 2020||-||File Read|
|VPN Gateway||Cisco||ASA||Jul 2020||-||File Read|
|VPN Gateway||F5||BIG IP||Jun 2020||-||RCE|
|Webserver||Apache||Tomcat||Feb 2020||Ghostcat||File Read|
|Logging library||Apache||Log4j||Dec 2019||-||RCE|
|Email service||Exim||Exim||Jul 2019||-||RCE|
|VPN Gateway||Fortinet||FortiGateway SSL VPN||May 2019||-||File Read|
|VPN Gateway||Pulse||Connect Secure||May 2019||-||File Read|
|Web Server||Adobe||Coldfusion||Sep 2018||-||RCE|
|Web Framework||Apache||Struts||Aug 2018||-||RCE|
|Web Server||Oracle||Weblogic||Jul 2018||-||RCE|
|Web Framework||Apache||Struts||Sep 2017||-||RCE|
|Web Framework||Apache||Struts||Jul 2017||S2-048||RCE|
|Utility||GNU Project||Bash||Sep 2014||Shellshock||RCE|
Artefacts are data from the target system which Sniper automatically extracts after one of the exploits succeeds. Their purpose is to provide solid proof that the target is vulnerable and to help in further manual exploitation, if necessary.
The artefacts are extracted by running predefined shell commands on the target, depending on its operating system. For instance, to extract the current user on a Linux system, the extractor will run the command
whoami whereas on Windows it will run the command
This is the list of artefacts that Sniper is able to extract:
|Current user||The name of the current system user that the exploit code is running as (e.g. root, Administrator or www-data).|
|System information||Information about the operating system like OS type, version, kernel, processor architecture, memory size, etc.|
|List of local users||A listing of the users currently configured on the operating system (e.g. from /etc/passwd)|
|List of running processes||A listing of the operating system processes that are currently running.|
|Network configuration||The settings of the network interfaces of the target machine (e.g. IP address, network mask, default gateway, etc.)|
|Network neighbors||A list of devices existent in the same local network as the target (layer 2).|
|Network connections||The list of open ports and established TCP connections of the target with other systems in the network.|
|Target||Specifies the system that will be scanned. Target can be an IP address, hostname or an URL.|
|Ports to scan||These are the ports that Sniper will try to automatically fingerprint and attack. Can be specified as common ports, range or list.|
How it works
Sniper runs a number of predefined steps for each target:
1. Scanning for open ports
This is the first phase the attack, which checks if the TCP ports specified as input are open or not. The result of this phase is a list of open ports, together with the protocol, type of service and its version.
2. Fingerprinting web services
Next, Sniper iterates through each port that runs a HTTP/S service and tries to determine what type of web application is running, whether it is a standard app (e.g. Outlook Web Access, VMWare web interface, etc.) and which technology sits behind it. This information is needed to select the appropriate exploit to run against it.
3. Looking for compatible exploits
Based on the fingerprint data about the target system, Sniper then filters a list of possible compatible exploits that match it.
4. Checking if the target is vulnerable
At this stage, the tool runs the check routine for each compatible exploit that determines whether the target is exploitable – without extracting any data.
5. Exploiting and extracting all artefacts
If the previous step succeeds and the target is exploitable, Sniper automatically proceeds to extract all the artefacts and show them in the output report.
6. Cleaning up
Most exploit modules do not create any files or processes on the target system so no cleanup is necessary. However, when they do, Sniper makes sure that they are deleted, so the system is left unaltered and clean.