full-disclosure - Re: MySQL trick for SQL injection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5540.1257525448@turing-police.cc.vt.edu>
Date: Fri, 06 Nov 2009 11:37:28 -0500
From: Valdis.Kletnieks@...edu
To: Paul Schmehl <pschmehl_lists@...rr.com>
Cc: Full disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: MySQL trick for SQL injection

On Fri, 06 Nov 2009 10:04:54 CST, Paul Schmehl said:
> What privileges did the user who performed the select have?
> 
> INTO OUTFILE is a dangerous routine (as you've clearly demonstrated), but that 
> privilege must be specifically granted to a user before it's possible to 
> execute it.  No sensible administrator would grant the FILE privilege to a 
> webserver application's database acccount.

Very true, but a good blackhat always keeps a good supply of ways to exploit
common stupid administrator mistakes.  I'd not be surprised in the least if
more than 10% of the sites, some admin under time pressure to Just Fix It
assigned FILE privs to get the web application back up and running.

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/