Submit your breaking news stories and original articles to us by contacting us
We all know about the security threat of non-sanitized user input, but it’s pretty scary how much a hacker can learn about your database structure just through SQL injections. This article, one of the most interesting I’ve read in a long time, shows how easy it is to gain access to an intranet area.
A customer asked that we check out his intranet site, which was used by the company’s employees and customers. This was part of a larger security review, and though we’d not actually used SQL injection to penetrate a network before, we were pretty familiar with the general concepts. We were completely successful in this engagement, and wanted to recount the steps taken as an illustration.
What “Countermeasures” Really Means
Superman: Brainiac Attacks! Review
Paypal Feels the Google Threat
Fingerprinting webserver attacks #2
Fingerprinting webserver attacks #1
Forever Geek is a resource for all things geek. You can stay tuned by having the latest FG news delivered to you for free via RSS.
Category: Uncategorized
Tags:
Five concept watch designs that make you calculate the time
Steam: Diplomacy of Digital Downloads over Retail Boxes
Best of CES 2010 (Part One): 3DTV, Audio, Display, Processors, Gadgets
A Decade of Zombies IV: Epidemic Rooted in Society
3 Responses for "SQL Injection Attacks by Example"
January 6th, 2005 at 00:26
1There was an even more interesting webcast (infact, there are several) on MSDN a while back about different penetrative techniques.
The presenter gave several demos of utilising the UNION command when returning data to query the system tables and extract specific details about the tables, their columns and stored procedures in the database.
January 10th, 2005 at 07:59
2very nice article. but when programming the interface to a backend. Wouldnt u first grab the user input then format it in someway.
I mean im no expert on the sql stuff but when i did a couple web programs at uni that’s the approach i took. It seemed the most logical.
But then again when uve got ur boss on ur shoulder…
January 11th, 2005 at 11:06
3Yeah, lok-lok, it’s definitely best to sanitize any user input before using it in queries. Of course, beginning PHP programmers don’t always think of that.
I just thought it amazing how much someone could learn about a database knowing only basic SQL injection techniques.
RSS feed for comments on this post
Leave a reply