Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

10/28/2009
03:38 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

Know Your Tools

Ever have one of those days where nothing really seems to go right? You're working on something that should be simple and it ends up throwing seemingly unexplainable errors back at you no matter what you try? Then when it does work, you're not sure what you changed that fixed it. Yeah -- me, too.

Ever have one of those days where nothing really seems to go right? You're working on something that should be simple and it ends up throwing seemingly unexplainable errors back at you no matter what you try? Then when it does work, you're not sure what you changed that fixed it. Yeah -- me, too.I'm currently working on a Web application vulnerability assessment. It's one I looked at years ago, but a lot of changes have been made since then and they want a fresh look at it. The task sounds easy enough, even though it is a relatively complex application. To save time, I decided to chain together the inline Web proxies I usually use for Web app testing. Good idea, bad implementation.

I started out with my Web app testing profile in Firefox fully "weaponized" per the Samurai WTF Add-Ons Collection I wrote about last week in "Firefox Web Browser Weaponization Redux." Next, I configured it to go through Burp Suite's Proxy. This is my normal setup when testing, but to streamline testing, I added ratproxy into the mix. Now my Web requests would start in Firefox, get proxied through Burp Proxy to ratproxy, which would then pass my requests to the target Web server. Simple, right?

Heck no! I kept logging into the Web app only to be denied again and again. I sent e-mail to the developers to confirm my credentials were correct and they said they were. So I tried logging in with my normal Firefox user profile and no proxies. Voila! The creds worked. Watching the login through Tamper Data cause a light to go on: NTLM authentication.

It turns out that as awesome as ratproxy is, it does not support NTLM authentication. Burp Proxy does support NTLM, but I had to read the documentation on how to enable it properly. Now as I'm walking through the Web app, my requests go from Firefox to ratproxy and on through Burp Suite.

To add to the fun, I'm also running Nikto (new version released on Oct 18) through ratproxy and Burp Suite. Now I've got multiple tools handling logging, two of which are looking for vulnerabilities. Ratproxy is checking passively, Nikto is actively scanning for know issues.

The moral of the story: know your tools. I wasted at least 30- to 45 minutes because I didn't know ratproxy lacked support for NTLM authentication and wasn't configuring it properly in Burp Suite. In my defense, out of about a hundred Web apps I tested, this is the only one to use NTLM authentication.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.