[+] Credits: hyp3rlinx
[+] Website: hyp3rlinx.altervista.org
[+] Source: http://hyp3rlinx.altervista.org/advisories/DOT-DEFENDER-CSRF.txt
Versions: 5.00.12865 / 5.13-13282
dotDefender is a Web application firewall (WAF) for preventing hacking attacks like XSS, SQL Injections, CSRF etc...
that provides Apache and IIS Server Security across Dedicated, VPS and Cloud environments. It meets PCI Compliance and also
provides E-Commerce Security, IIS and Apache Security, Cloud Security and more.
Cross Site Request Forgery - CSRF
Dotdefender firewall (WAF) is vulnerable to cross site request forgery, this allows attackers to make HTTP requests via the victims browser to
the dotdefender management server on behalf of the victim if the victim is logged in and visits a malicious web page or clicks an infected link.
Result can be modifying or disabling various firewall patterns, User-Defined Rule settings and global event logging etc...
HTTP requests sent to Dotdefender to enable or disable user-Defined rule settings are base64 encoded using SOAP protocol.
Sending the below base64 value for example disables a Dotdefender firewall setting.
Tested successfully on Windows & Linux:
dotDefender Version: 5.00.12865
Web Server Type: Microsoft-IIS
Server Operating System: Windows
Web Server Version: 7.5
Firefox web browser
dotDefender Version: 5.13-13282
Web Server Type: Apache
Server Operating System: Linux
Example to send requests to disable firewall rule settings that defends against SQL injection.
We need to send two requests first to modify the desired settings and second to commit our changes.
HTTP request 0x01 - send following soap request to disable SQL Injection request firewall rule
HTTP request 0x02 - send the next request to commit the changes
Other SOAP payload examples for rule disabling:
this is disable a rule #19, send the below request to disable remote IP protections:
disable rule 20:
Finally commit them with below request:
initial report 11/16/2015
vendor response 11/20/2015
vendor delays for two months
1/19/2016 Vendor finally acknowledges vulnerability
inform vendor of disclosure date
vendor no longer responds
Feb 8, 2016 : Public Disclosure
Request Method(s): [+] POST
Vulnerable Product: [+] DotDefender v5.0 & v5.13
Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author.
The author is not responsible for any misuse of the information contained herein and prohibits any malicious use of all security related information or exploits by the author or elsewhere.
# Iranian Exploit DataBase = http://IeDb.Ir [2016-02-11]