waffit integration. #290

Activity

1. stamparm commented on Dec 12, 2012

   

   stamparm

   on Dec 12, 2012

   Member

   More actions

   It's a cool tool, but looks unmaintained for some time. Now, personally, I believe that sqlmap would profit from using same logic inside (detecting backend WAFs), but I am also scared that it would be too strenuous to maintain along with other stuff.

   IMO, I am for (new from glance) implementation into our code (code from there uses it's custom connection wrappers) using "testing vectors" from there - slow implementation with LOW priority.

   p.s. an idea of using a modular approach like in "tamper scripts" comes to my mind ;)
2. antisnatchor commented on Dec 13, 2012

   

   antisnatchor

   on Dec 13, 2012

   More actions

   It is unmaintained Miro, you're right.
   Implementing new code, maybe partially based on waffit techniques would be better IMHO.
3. ghost assigned

   bdamele

   on Dec 18, 2012
4. ghost assigned

   stamparm

   on Feb 21, 2013
5. stamparm

   added 5 commits that reference this issue on Feb 21, 2013

   Update for an Issue #290 (adding tamper-like scripts into (new) direc…

   ...

   6b2981e

   Finalizing implementation for an Issue #290

   8e49872

   Minor refactoring for an Issue #290

   08f0670

   Unhidding switch '--identify-waf' (Issue #290)

   29ba43e

   Update for an doc/THANKS (Issue #290)

   fc554e5
6. stamparm commented on Feb 21, 2013

   

   stamparm

   on Feb 21, 2013

   Member

   More actions

   Added new switch --identify-waf. Principle is similar as with --tamper. All scripts from waf directory are run against the target to identify the WAF/IDS/IPS product. Currently there are 16 of those implemented. Big thanks goes to @whenov ;)
7. stamparm commented on Feb 21, 2013

   

   stamparm

   on Feb 21, 2013

   Member

   More actions

   p.s. all requests in this checking are cached so there are no unnecessary requests going on.
8. antisnatchor commented on Feb 21, 2013

   

   antisnatchor

   on Feb 21, 2013

   More actions

   Nice one ;-)
   I will try it soon.

   ---

   Miroslav Stampar mailto:notifications@github.com
   February 21, 2013 1:57 PM

   Added new switch |--identify-waf|. Principle is similar as with
   |--tamper|. All scripts from |./waf| directories are run against the
   target to identify the WAF/IDS/IPS product. Currently there are 16 of
   those implemented. Big thanks goes to @whenov
   https://github.com/whenov ;)

   —
   Reply to this email directly or view it on GitHub
   #290 (comment).
9. champ1 commented on Feb 21, 2013

   

   champ1

   on Feb 21, 2013

   More actions

   fucking great..:)

   I look forward too auto use tamper script based on waf output.. hehe

   Thx guys..:)
10. stamparm

    closed this as completedon Feb 26, 2013
11. stamparm

    added a commit that references this issue on Feb 26, 2013

    Minor update for an Issue #290

    f6b43b4
12. stamparm commented on Feb 26, 2013

    

    stamparm

    on Feb 26, 2013

    Member

    More actions

    There was a "bug" involved prior to commit f6b43b4 in "Set-Cookie" based WAF scripts. Now fixed.
13. stamparm commented on Feb 27, 2013

    

    stamparm

    on Feb 27, 2013

    Member

    More actions

    $ ls -1 sqlmap/waf
    
    airlock.py
    barracuda.py
    bigip.py
    binarysec.py
    ciscoacexml.py
    cloudflare.py
    datapower.py
    denyall.py
    dotdefender.py
    hyperguard.py
    incapsula.py
    __init__.py
    isaserver.py
    modsecurity.py
    netcontinuum.py
    netscaler.py
    profense.py
    proventia.py
    secureiis.py
    teros.py
    trafficshield.py
    uspses.py
    webappsecure.py
    webknight.py
    
14. kirtixs commented on Feb 27, 2013

    

    kirtixs

    on Feb 27, 2013

    Contributor

    More actions

    Wow, very nice :)