News for hackers. Stuff that matters.
Re:A Big Case of Oops by Quarrelsome on Friday February 26, 2010 @09:29AM (#1153167)
How did you dig that one backwards... ? As far as I could tell you only had an image of the site.....?
Re:A Big Case of Oops by whyleyc on Friday February 26, 2010 @09:35AM (#1153184)
Yep just from images (and Google) - I examined one of the images from the post at a higher resolution (by clicking on it) and took a look at the map on the right-hand side.

It was a map of Thailand, so that gave me the type of restaurant. From there it was just a simple Google query combining that knowledge with the URL structure revealed in the blog post:

http://www.google.co.uk/search?q=thai+restaurant+locationid%...

Then it was just a case of working through the list of possibilities (it was second on that list) :-)

Re:A Big Case of Oops by DougBTX on Friday February 26, 2010 @11:59AM (#1153511)
Good searching. Looks like you've found quite a few more vulnerable sites too.
Re:A Big Case of Oops by dacort on Friday February 26, 2010 @02:54PM (#1153963)
I would wager to say a large majority of .asp sites out there are vulnerable to these types of issues.

Most were coded before common sanitization and security practices were observed during dev, not to mention built in to frameworks.

Re:A Big Case of Oops by 3ds on Friday February 26, 2010 @09:56PM (#1154787)
Re:A Big Case of Oops by BigZaphod on Friday February 26, 2010 @11:19AM (#1153407)
Obviously he just zoomed in and kept saying "enhance image" to his computer until the answer was revealed in a tiny shadow on one of the pixels...
Re:A Big Case of Oops by MicahWedemeyer on Saturday February 27, 2010 @10:01AM (#1155330)
Damn this thing and it's ability to only upvote once!
Re:A Big Case of Oops by lenni on Friday February 26, 2010 @09:31AM (#1153172)
Screenshot + TinEye?