tag:blogger.com,1999:blog-7060425936165350502.post778043743821382292..comments2023-12-18T06:04:34.536-08:00Comments on SharingSec: SQL Injection - enumerating Microsoft AD users using Oracle resourcesIsmael Goncalveshttp://www.blogger.com/profile/09091986047591004797noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7060425936165350502.post-39881100536461817272013-02-01T16:48:26.752-08:002013-02-01T16:48:26.752-08:00I got a virtual lab running a Windows Server 2012,...I got a virtual lab running a Windows Server 2012, Windows 7 clients and Oracle 11g2 on one of this clients, that might be the reason.Antonio Sánchezhttps://www.blogger.com/profile/15438153898388125592noreply@blogger.comtag:blogger.com,1999:blog-7060425936165350502.post-21556782558860214532013-02-01T15:16:08.222-08:002013-02-01T15:16:08.222-08:00Hi Sánchez!
First of all, thanks for comment. Well...Hi Sánchez!<br />First of all, thanks for comment. Well, maybe you didn’t get the two different strings because of the backend (e.g. AD version). If you look for it you will see there are LDAP backend that provide different messages in a way I have explained.Ismael Goncalveshttps://www.blogger.com/profile/09091986047591004797noreply@blogger.comtag:blogger.com,1999:blog-7060425936165350502.post-62773045291306187652013-01-28T16:35:18.116-08:002013-01-28T16:35:18.116-08:00Awesome post!
I've given it a shot to the whol...Awesome post!<br />I've given it a shot to the whole thing, and almost everything works as described here, just one small detail.<br /><br />The string 'data 52e' does not change when I provide either an invalid username or password. I guess that this would make a little bit more tedious the process of brute forcing.<br /><br />Antonio Sánchezhttps://www.blogger.com/profile/15438153898388125592noreply@blogger.com