[Full-Disclosure] RE: COELACANTH: Phreak Phishing Expedition]
From: Jelmer (jkuperus_at_planet.nl)
To: "'Thor Larholm'" <email@example.com>, "'Drew Copley'" <dcopley@eEye.com>, firstname.lastname@example.org, email@example.com Date: Sat, 12 Jun 2004 00:22:19 +0200
Almost correct, though not quite, I fired up a packetsniffer while clicking
the link and witnessed a dns lookup taking place
Standard query www.jelmer.com?redir=www.e-gold.com
This actually resolves to e-gold As you can see
C:\ >ping www.jelmer.com?redir=www.e-gold.com
Pinging www.jelmer.com?redir=www.e-gold.com [188.8.131.52] with 32 bytes
This is because they have setup wildcard dns for e-gold.com
So the combination ignore host header *AND* wildcard dns leads to an
Tmf.nl for instance uses wildcard dns but complains about a malformed Host
<a href="http://www.microsoft.com%2F redir=www.tmf.nl">test</a>
From: Thor Larholm [mailto:firstname.lastname@example.org]
Sent: vrijdag 11 juni 2004 3:10
To: Drew Copley; email@example.com; firstname.lastname@example.org
Subject: RE: COELACANTH: Phreak Phishing Expedition]
You can't replicate this with most other servers because the Host header
is set to a non-existant site on most servers.
Whenever IIS or Apache receives a request it will first locate the
proper site based on the IP adress being used, after which it will
lookup based on the Host header. In the case of e-gold, they have simply
not specified a Host header for the IIS website that they configured.
You can send a HTTP request to e-gold.com with "Host: foobar" and their
site still comes up, even though you should only get their site with a
header such as "Host: e-gold.com" or "Host: www.e-gold.com".
HTTP 1.1 requires the use of a Host header and it is bad practice to
accept HTTP requests without a Host header that corresponds to a locally
configured site. In most cases with IIS, this only happens if you are
using the Default Website or explicitly has choosen to not specify a
Host header for the site. You can specify multiple Host headers for a
site so there is not much excuse not to do so.
Whenever IE wants to send an HTTP request it first needs to determine
what server to connect to. Because of the URL escaping IE disregards
anything before the slash and equal sign, and sees that it has to send
an HTTP request to www.e-gold.com. It is only after IE has determined
what server to request information from that it URL decodes the URI and
ends up with http://www.microsoft.com/redir=www.e-gold.com, which it
then displays in the Address Bar and subsequently uses to determine what
security zone it should use to render the HTML. IE only decides what
security zone to use based on the Address Bar value after it has
successfully downloaded all of the HTML (untill then it is in the
Unknown Zone), at which point the URL decoding has long since happened.
If you want to exploit this to serve content from your site in the
security zone of another site, you will need to disregard the Host
header being sent by the client. A perfect candidate you can use to gain
additional privileges is WindowsUpdate.microsoft.com or
oca.microsoft.com who are both in the Trusted Sites security zone on a
default installation of Windows Server 2003 and Windows XP SP2.
You should be able to use this to compromise Windows XP SP2 through
Internet Explorer despite the My Computer zone hardening since the
Trusted Sites Zone has all of the privileges you need to plant and
execute a file.
Senior Security Researcher
24 Corporate Plaza #180
Newport Beach, CA 92660
Stock symbol: (PIVX)
Phone: +1 (949) 231-8496
6BB1 B77F CB62 0D3D 5A82 C65D E1A4 157C 5A27 6569
PivX defines a new genre in Desktop Security: Proactive Threat
From: Drew Copley [mailto:dcopley@eEye.com]
Sent: Thursday, June 10, 2004 4:40 PM
To: email@example.com; firstname.lastname@example.org
Subject: RE: [Fwd: [Full-Disclosure] COELACANTH: Phreak Phishing
> Subject: [Full-Disclosure] COELACANTH: Phreak Phishing Expedition
> From: "email@example.com" <firstname.lastname@example.org>
> Date: Thu, June 10, 2004 12:35 pm
> To: email@example.com
> Thursday, June 10, 2004
> The following was presented by 'bitlance winter' of Japan today:
> Quite inexplicable from these quarters. Perhaps someone with server
> 'knowledge' can examine it.
> It carries over the address into the address bar:
> [screen shot: http://www.malware.com/gosh.png 72KB]
> while redirecting to egold. The key being %2F without that it fails.
> The big question is where is the 'redir' and why is it only applicable
> [so far] to e-gold. Other sites don't work and e- gold is running an
> old Microsoft-IIS/4.0.
IE makes this into a connection with e-gold.com like so:
GET / HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/msword, application/x-shockwave-flash, */*
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR
1.1.4322; .NET CLR 1.0.3705)
Host: www.microsoft.com/ redir=www.e-gold.com
It never touches microsoft.com.
What is interesting, though, is IE spoofs the zone. If you change
www.microsoft.com in there to a site in your trusted zone, you will see
e-gold read as your trusted zone.
So, you should be able to bounce from any trusted zone and theoritically
from local zone -- and with adodb still being open, you should be able
to run code because of the open adodb issue.
IE doesn't talk to e-gold first. It connects to it. It sends the GET
request, it receives the first page.
But, can't replicate with other servers. It requires some more research.
> Working Example:
> credit: 'bitlance winter'
> End Call
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
Full-Disclosure - We believe in it.
Full-Disclosure - We believe in it.