Attack Surface Management With Sn1per Professional

Continuous Attack Surface Management (ASM) and reduction has become a crucial function for every organization to gain visibility of their perimeter security. Having the right tools and processes in place is vital to detecting new vulnerabilities before attackers do. In this blog post, we will outline the basic steps for discovering the attack surface with Sn1per Professional v9.0.


IPSwitch MoveIt Stored Cross Site Scripting (XSS)

Date: 1-31-2017
Software Link:
Affected Version: 8.1-9.4 (only confirmed on 8.1 but other versions prior to 9.5 may also be vulnerable)
Exploit Author: [email protected]
Vendor Homepage:
Category: Webapps
Attack Type: Remote
Impact: Data/Cookie Theft


IPSwitch MoveIt v8.1 is vulnerable to a Stored Cross-Site Scripting (XSS) vulnerability. Attackers can leverage this vulnerability to send malicious messages to other users in order to steal session cookies and launch client-side attacks.

Proof of Concept

The vulnerability lies in the Send Message -> Body Text Area input field.

POST /human.aspx?r=692492538 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Connection: close
Content-Type: application/x-www-form-urlencoded
Content-Length: 598



Update to version 9.5

Disclosure Timeline

1/30/2017 – Disclosed details of vulnerability to IPSwitch.
1/31/2017 – IPSwitch confirmed the vulnerability and verified the fix as of version 9.5 and approved public disclosure of the vulnerability.

CVE-2016-4401 – Unauthenticated Database Credential Leak In Aruba ClearPass

It is possible for an unauthenticated user with network access to a ClearPass server to expose database credentials.  
This vulnerability leads to complete system compromise.

Severity: CRITICAL
CVSSv3 Overall Score: 9.8

Discovery: This vulnerability was discovered by [email protected] and reported through the BugCrowd managed bug bounty

FIX: Fixed in 6.5.7 and 6.6.2

Bounty: $1,500

Zabbix 2.2.x, 3.0.x SQL Injection/RCE 0day Vulnerability

Title: Zabbix 3.0.3 SQL Injection Vulnerability
Product: Zabbix
Vulnerable Version(s): 2.2.x, 3.0.x
Fixed Version: 3.0.4
Patch link:
Credit: [email protected]
Vendor Description:
Zabbix is an open source availability and performance monitoring solution.
Vulnerability Overview:
Zabbix 2.2.x, 3.0.x and trunk suffers from a remote SQL injection vulnerability due to a failure to sanitize input in 
the toggle_ids array in the latest.php page.
Business Impact:
By exploiting this SQL injection vulnerability, an authenticated attacker (or guest user) is able to gain full access 
to the database. This would allow an attacker to escalate their privileges to a power user, compromise the database, 
or execute commands on the underlying database operating system.
Because of the functionalities Zabbix offers, an attacker with admin privileges (depending on the configuration) can 
execute arbitrary OS commands on the configured Zabbix hosts and server. This results in a severe impact to the 
monitored infrastructure.
Although the attacker needs to be authenticated in general, the system could also be at risk if the adversary has no 
user account. Zabbix offers a guest mode which provides a low privileged default account for users without password. 
If this guest mode is enabled, the SQL injection vulnerability can be exploited unauthenticated.
Proof of Concept:
latest.php?output=ajax&sid=&favobj=toggle&toggle_open_state=1&toggle_ids[]=15385); select * from users where (1=1
SQL (0.000361): INSERT INTO profiles (profileid, userid, idx, value_int, type, idx2) VALUES (88, 1, 
'web.latest.toggle', '1', 2, 15385); select * from users where (1=1)
latest.php:746 → require_once() → CProfile::flush() → CProfile::insertDB() → DBexecute() in /home/sasha/zabbix-
Disclosure Timeline:
7/18/2016 - Reported vulnerability to Zabbix
7/21/2016 - Zabbix responded with permission to file CVE and to disclose after a patch is made public
7/22/2016 - Zabbix released patch for vulnerability
8/3/2016 - CVE details submitted
8/11/2016 - Vulnerability details disclosed