guys, stay off ES5, it's BAD to da BONE. I
stumbled on this while cruising the waves of
the net.
http://www.zeropaid.com/news/articles/auto/10022003i.php
EarthStation 5 P2P application contains
malicious code
posted by random nut on October 02, 2003 @
11:14am
ES5 info
EarthStation 5 (aka ES5, aka ESV) (
http://www.earthstation5.com and
http://forums2.es5.com/) is a P2P
application first released about 6-12 months
ago. The people behind ES5 claim that ES5 is
the most secure P2P software in the world.
They also claim that they are security
experts, and that they have more than 15
million simultaneous users on-line 24/7. In
comparison Kazaa, the most popular P2P
application, only has about 4 million
simultaneous users on-line at any given time
of day.
Malicious code
There exists malicious code in ES5.exe's
"Search Service" packet handler. By sending
packet 0Ch, sub-function 07h to the "Search
Service"'s IP

ort, a remote attacker could
delete any file the user is sharing. If the
remote attacker uses "filenames" with a
relative path in them (eg.
"......WINDOWSNOTEPAD.EXE"), the remote
attacker could also delete files in eg. the
windows and windowssystem32 folders, or any
other folder on the same partition as any of
the shared folders. Since most users using
Windows are in the Administrators group, a
remote attacker could also delete the
C:BOOT.INI file which is a required boot
file used by ntldr.
IMPORTANT: This is not a bug! They
intentionally added this code to ES5.
Vulnerabilities
There also exists a lot of other
vulnerabilities in ES5 (eg. DoS attacks,
buffer overflow bugs, and so on), but these
all seem to be unintentional. Another
advisory may have more info on these
vulnerabilities, but I'm not their beta
tester so don't hold your breath.
Conclusion
The people behind ES5 have intentionally
added malicious code to ES5. If you have
followed the ES5 discussions on message
boards and read what the ES5 people have
said and done (eg. DoS attacking BitTorrent
sites), this comes as no surprise. The
question then is "why did they do it?" I'm
sure they won't tell us, but here's a
theory: They could be working for the RIAA,
MPAA, or a similar organization. Once they
have enough users on their ES5 network, they
would start deleting all copyrighted files
they own which their users are sharing. The
users wouldn't know what hit them.
Tested ES5 builds
ES5 build 1266
ES5 build 2180 (latest version)
MD5 sums of files
MD5 sum (using RFC 1321 source code) of
tested files (just in case the ES5 people
will remove the malicious code w/o changing
the build number)
e35838ef6668abe883344e3a7e734794
*es5beta1266.exe
ce44a1f0542b9132f2debd9866febc65
*es5beta2180.exe
373c30ba0e8b1dce05dcab2acce94a77
*es5_build1266.exe
915de0f8e72be40bf071a86bc9dc2626
*es5_build2180.exe
2,244,663 es5_build1266.exe (ES5.exe - build
1266)
2,347,063 es5_build2180.exe (ES5.exe - build
2180 - latest version)
4,436,309 es5beta1266.exe (ES5 installer -
build 1266)
4,553,325 es5beta2180.exe (ES5 installer -
build 2180 - latest version)
The official ES5 installer download URL is
http://download.es5.com/es5beta.exe , but
check its MD5 sum before installing it in
case they changed it.
Credits
me

for discovering it (randnut@yahoo.com)
Exploit code
Go to
http://www.geocities.com/esvuln to
download the exploit binary if you don't
want to compile it yourself.
Source code to esv ("ExpoitStation 5" or
"EarthStation Vulnerabilities", you decide)
but first a little FAQ...
Uninstall Instructions
Kill all ES5.exe processes with task manager
(taskmgr.exe)
Try ES5's uninstaller
Delete registry key
HKEY_CURRENT_USERSoftwareHelmuthSpeakingForBo
sko ne
Delete registry key
HKEY_LOCAL_MACHINESOFTWAREEarthStation5
Remove the ES5 entry from
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurr
e ntVersionRun to stop it from running after
reboot
Remove the ES5 entry from
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCur
r entVersionRun to stop it from running
after reboot
Delete all files in the ES5 folder (usually
in "C

rogram FilesEarthStation5"). If files
can't be deleted, boot into safe mode and
delete them.
Restart computer
Now I wouldn't believe Random Nut that soon,
as he is one of the key developers of Klite
(=opposition of ES5), but this story will
put things in very gloomy light.
http://www.gonze.com/index.cgi/2003/08/02#8-2-3
Sat, 02 Aug 2003
Anatole says:
So I just tried installing ES5 on my Windows
machine. The first thing
it did is attempt to connect to an IP in the
Gaza Strip. The
administrator for that IP block is someone
with an earthstationv.com
email address. Then my keylogger warning
program popped up and
complained that the program had attempted to
hook to my keyboard. I
killed it, and ran an uninstall. The
uninstall failed because some of
its DLL's were still 'in use' despite no
matching processes. I rebooted
and was able to do a successful uninstall
manually. Afterwards, I
checked my registry and removed a fresh
entry from "Intertrust," a
company that makes DRM software.
Overall, an entertaining experience.
The earthstation5 folks strike me as sleazy.
NOW THAT SOUNDS DOWNRIGHT ALARMING!!!!
Or how about
http://www.securitynewsportal.com/cgi-bin/cgi-script/csNews/csNews.cgi?database=JanCC%2edb&command=viewone&id=47
EarthStation 5 P2P application contains
malicious code - Not a bug - It was
deliberate
This is not a bug! They intentionally added
this code to ES5
10-03-2003 09:15:30 AM CST -- from the Full
Disclosure mailing list
EarthStation 5 (aka ES5, aka ESV) (
http://www.earthstation5.com and
http://forums2.es5.com/) is a P2P
application first released about 6-12 months
ago. The people behind ES5 claim that ES5 is
the most secure P2P software in the world.
They also claim that they are security
experts, and that they have more than 15
million simultaneous users on-line 24/7. In
comparison Kazaa, the most popular P2P
application, only has about 4 million
simultaneous users on-line at any given time
of day. There exists malicious code in
ES5.exe's "Search Service" packet handler.
By sending packet 0Ch, sub-function 07h to
the "Search Service"'s IP

ort, a remote
attacker could delete any file the user is
sharing. If the remote attacker uses
"filenames" with a relative path in them
(eg. "..\..\..\WINDOWS\NOTEPAD.EXE"), the
remote attacker could also delete files in
eg. the windows and windows\system32
folders, or any other folder on the same
partition as any of the shared folders.
Since most users using Windows are in the
Administrators group, a remote attacker
could also delete the C:\BOOT.INI file which
is a required boot file used by ntldr.
There also exists a lot of other
vulnerabilities in ES5 (eg. DoS attacks,
buffer overflow bugs, and so on), but these
all seem to be unintentional. Another
advisory may have more info on these
vulnerabilities, but I'm not their beta
tester so don't hold your breath. The people
behind ES5 have intentionally added
malicious code to ES5. If you have followed
the ES5 discussions on message boards and
read what the ES5 people have said and done
(eg. DoS attacking BitTorrent sites), this
comes as no surprise. The question then is
"why did they do it?" I'm sure they won't
tell us, but here's a theory: They could be
working for the RIAA, MPAA, or a similar
organization. Once they have enough users on
their ES5 network, they would start deleting
all copyrighted files they own which their
users are sharing. The users wouldn't know
what hit them....continued...
Click here to read the full report in the
Full Disclosure mailing list at Insecure.org
UPDATE : Within a few short hours of this
story hitting the media the folks over at
ES5 scrambled and uploaded a new ES5
installer. The new installer has not been
tested yet, but you can be pretty sure that
they have removed their malicious code and
will soon claim that the original reports
about them putting malicious code in their
P2P warez were lies... We shall see what
they "officially claim happened. Builds 1266
and build 2180 were the ones tested and
found to contain malicious code
And now the question is : How many of the
ES5 users will dump that software off their
machines and how many will continue blindly
trusting ES5 to be ethical.. My bet is that
the majority of them are so addicted to
sucking down free movies and tunes that they
probably have no idea what risk their
computers were put at. I hate the RIAA as
much as anyone, but to deliberately choose
to run an 'untrustworthy' warez is just
foolish. Nuff said.