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]
Date: Wed Jul  5 01:41:58 2006
From: xploitable at gmail.com (n3td3v)
Subject: Re: Google and Yahoo search engine zero-day code

On 7/4/06, n3td3v <xploitable@...il.com> wrote:
> Exploit: Zero-day
>
> Status: High
>
> Type: Hi-Jack corporate crawler machines which have vulnerable robot
> cahcing software installed
>
> We've issued two zero-day warnings so far, OneCare and Cisco Systems
>
> Today's disclosure involves Google and Yahoo search engines:
>
> All you need to do is put in the code to a web page, when Google and
> Yahoo visit it, then the code exploits the software they use and makes
> them start caching 'other' pages. Including 'no index' pages, where
> sites have setup a robot text file on their server to protect
> corporate and consumer interests. We already gave an example of this
> earlier.... http://groups.google.com/group/n3td3v/browse_thread/thread/542b78eaabea015a/5b1c58ab92b11c4f
> The exploit allows you to insert 'arbitrary' code, which also means
> denial of service or 'crash' for short.
> This means the profit of GOOG and YHOO are compromised, but MOREOVER
> (Hi robert lemos) this means you can get Google and Yahoo to cache
> sensitive data. The cached data isn't avaiable to the public per say,
> because in the 'arbitrary' code, you assign a special encryption to
> the cache, that only the hacker knows. This means specific users use
> the search engine, with a robot to automatically harvest the exploited
> data..... this part of the attack is possible because Google and Yahoo
> don't have 'word verfication' on all search queries.
> MOREOVER (Hi robert lemos), the compromised data, to which we exploit
> is used to break into Google and Yahoo, ebcause we have a list of all
> the corporate users logged in. However, all web servers are
> vulnerable, but our focus is Google and Yahoo employees.... you can
> use the exploit to get credit cards and other evils.
>
> Take care
> n3td3v research branch
>
> Google and Yahoo did not take our original seriously, so we
> re-allocate their memory today.
>
> This is ciritcal, but Henri and Mark don't talk to me anymore on Yahoo
> Messenger, so we can't pass info across to the vendor... and the
> security@...oo-inc.com address you get no reply, so, its upto the
> international security community now for Google and Yahoo to get this
> patched once and for all.
>
> http us today at n3td3v.googlepages.com
>
> We work our wicked ways......
>

1. insert exploit code into server

2. wait for google and yahoo

3. access key set once bot reaches your page, this lets n3td3v
research branch access our exploied data via search.yahoo.com (a key
is assigned, so noone else can query our data by accident, this acts
as a password for the search data.

4. Our bot goes to search.yahoo.com with matching access key, and
grabs data... is served back to our database, where we then use this
data to access corporate and consumer accounts, and do specialized
harvesting of the type of data we've grabbed from the Yahoo and Google
servers.

5. We define the different types of consumer and corporate data thats
arrived on our database server, allowing us to further filter and tag
different types of data, this then allows us to 'search our' database
on demand for corporate and (or) corporate data.

6. We have world domination, and Google and Yahoo cannot detect the
malicious with their conventional aduit methods, because we asked our
inside contacts.

Happy coding.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ