Paid Advertising
web application security lab

Greater Precision in Timing Attacks Using DoS

Because of all of the stuff that happened over the last week or so regarding Slowloris, I started thinking about other ways to use DoS to aid in existing attacks. A lot of times it’s really the opposite of what an attacker wants to do. Typically the attacker wants to keep the system alive so they can steal information from it or break into it. The more it stays up the better.

As I mentioned a few days ago, there is one way you can use the site by keeping a session open that you initiated prior to the attack, so that essentially you are the only person on the system - or one of only a handful at best. Well one place this helps you is with timing attacks. If you know a system tends to react to load because of the heavy database calls or you just aren’t certain what the effect of a lot of users are, you have an option - denial of service.

By denying service to everyone except you, you can remove the bandwidth and database chatter, and give you far more precise information about what is going on at the code and database levels. By examining the timing differences between a valid username that you know exists and an invalid one you know cannot exist you can create lists of valid usernames, or at minimum identify what the timing should be for both use cases with and without load. Again, this is another virtue of a DoS attack that leaves you alone on the system but stops everyone else from connecting. Having no one else is there to pester you or give you erroneous results is a timing attack dream come true.

3 Responses to “Greater Precision in Timing Attacks Using DoS”

  1. LonerVamp Says:

    Typically it is the world of academia that delves into things like timing attacks or making assumptions based on sub-second responses. And I think many academia-based research tends to get filed under the “neat, novel, but impractical” bucket.

  2. Zac B Says:

    “neat, novel, but impractical” always has this disconcerting way of becoming “neat, repeatable, hard to cope with”.

    After all, “640k should be enough for everyone”.

  3. noob Says:

    interesting topic can someone post here a tutorial for CSRF attack?thanks…im very greatful if u someone teach me…email me at thanks in advance…