Gopher is a protocol developed at the University of Minnesota in the early 1990's. Gopher servers offer hierarchically organized directories and files. These form a "gopherspace" which can be thought of as the predecessor of the World Wide Web. Gopher was mostly abandoned soon after HTTP and the World Wide Web started gaining popularity. Microsoft Internet Explorer has a built-in gopher client. Gopher pages can be accessed via URLs starting with "gopher://". The part of code in IE which parses gopher replies contains an exploitable buffer overflow bug. A malicious server may be used to run arbitrary code on an IE user's system. When the overflow is triggered, a fixed sized buffer in stack gets overwritten with data from the gopher server. This data can contain most octets from 0 to 255 (also nulls) which makes it particularly easy to inject a working shellcode in it. This is a traditional, trivially exploitable buffer overflow. A test exploit has been successfully used to run arbitrary code without user intervention with various IE versions and systems including IE 5.5 and 6.0. The attack can be launched via a web page or an HTML mail message which redirect the user to a malicious gopher server when the victim views them. The server can be very minimal, ie. a program that can listen on a TCP port and write a block of data; a fully operational gopher server isn't necessary in order to carry out the attack. The exploiter could do anything that a regular user could do on the system: retrieve, install, or remove files, upload and run programs, etc. Full technical details aren't disclosed at this time to prevent exploitation. Microsoft was contacted on May 20th (US time). At the moment of writing this advisory, Microsoft has started designing and coding a fix, but hasn't given any approximation of when it would be released. Source: Online Solutions Oy