SA Security BloggersPopular EntriesArticles How-To's Papers Tools Neologisms SSLCertificate fingerprints: SHA1: 61 13 45 4B 4C F9 89 9B B7 87 C8 78 F7 38 12 CB 07 E2 60 BF HTTPS version. LicenseDisclaimer
This blog and its contents are in no way affiliated with, or endorsed by my employer.
|
Random Entry: Sun Recommended Patch Management Policy
< Currently, potentially, Infected SA sites | Debian (and derivatives) OpenSSL-based keys vulnerability > Monday, May 12. 2008SQL injections going madTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
This happened to our site... but I thought SQL injection only works on pages with forms ?
This happened to database tables that are only read to display content ?
Hi Philip,
There only needs to be one injection point, and that can be on *any* page displaying forms, or accepting GET/POST variables, or even WebServices.
Once they have an injection point, and if your DB isn't sufficiently secured, they can write to any content table the user in the connection string has access to write to. The current round seems to try and write to all of them.
Parameterise and pre-compile your SQL, then remove as many rights from the user you use to connect to the DB to solve this.
|
Quicksearchthis blog: Security Blogs |