from the attempt-to-head-off-a-ton-of-questions-to-misc@ dept.
Another Windows worm is on the loose. It's named Nimda, and naturally it targets IIS on NT/2k. Why, you ask, do I care?
Because I noticed during the whole 'Code Red' thing, that people kept sending log excerpts to
asking if they were being attacked. Now, granted the *.exe in the URL is a dead giveaway, but I'll still bet you this shows up on
. It spreads via multiple vectors, one of which is visiting an infected site using Internet Explorer. So think about that before you get curious and visit your *attacker* after they show up in your logs.
This is what the traffic looks like [*source address sanitized*]:
Subject: Nimda Worm
Date: Tue, 18 Sep 2001 18:49:43 -0600 (MDT)
From: Dave Ahmad
We have been receiving reports of a new worm from a large number of users.
Instead of deluging BUGTRAQ with traffic more appropriate for INCIDENTS,
we are posting a summary of the worm and the vulnerabilities it exploits:
A new worm named W32/Nimda-A (known aliases are Nimda,
Minda, Concept V, Code Rainbow) began to proliferate the morning of
September 18, 2001 on an extremely large scale that targets the Microsoft
Windows platform. It attempts to spread via three mechanisms; as an email
attachment, a web defacement download, and through exploitation of known
IIS vulnerabilities. Collateral damage include network performance
degradation due to high consumption of bandwidth during the propagation
process. There have been reports of Apache Servers being inadvertantly
affected by Nimda by being subjected to a denial of service condition (the
configuration of these servers is not known).
This worm takes advantage of multiple vulnerabilities
and backdoors. The worm spreads via e-mail and the web. Through the
e-mail vector, the worm arrives in the users inbox as a message with a
variable subject line. The e-mail contains an attachment named
'readme.exe'. This worm formats the e-mail in such a way as to take
advantage of a hole in older versions of Internet Explorer. Outlook
mail clients use the Internet Explorer libraries to display HTML e-mail,
so by extension Outlook and Outlook Express are vulnerable as well, if
Internet Explorer is vulnerable. The hole allows the readme.exe program
to execute automatically as soon as the e-mail is previewed or read.
Once it has infected a new victim, it mails copies of itself to other
potential victims, and begins scanning for vulnerable IIS Web servers.
When scanning for vulnerable IIS servers, it attempts to exploit the
Unicode hole (bid 1806) and the escaped characters decoding command
execution vulnerability (bid 2708). It also attempts to access
the system via the root.exe backdoor left by Code Red II. Once it
finds a vulnerable IIS server, it installs itself in such a way that
visitors to the now-infected web site will be sent a copy of a .eml
file, which is a copy of the e-mail that gets sent. If the victim is
using Internet Explorer as their browser, and they are vulnerable to the
hole, they will execute the readme.exe attachment in the same way as if
they had viewed an infected e-mail message.
Examination of the worm reveals the following attack strings
used to exploit IIS Web servers.
To those strings are added /winnt/system32/cmd.exe?/c+dir
Other attacks include:
It is believed that all of the vulnerabilities exploited by this worm are
The links below provide fix information. Administrators and users are
advised to apply patches as soon as possible. If further analysis
concludes that other vulnerabilities are involved, updated information
will be posted to the list.
Bugtraq ID: 2524 / CVE ID: CAN-2001-0154
Microsoft Security Bulletin MS01-020
Bugtraq ID: 2708 / CVE ID: CAN-2001-0333
Microsoft Security Bulletin MS01-026
Bugtraq ID: 1806 / CVE ID: CVE-2000-0884
Microsoft Security Bulletin MS00-078
Microsoft IIS Lockdown Tool:
For discussion of infection or attack attempts, subscribe to the INCIDENTS
mailing list. For discussion of the worm itself and others, FORENSICS and
FOCUS-VIRUS are more appropriate than BUGTRAQ.
I grabbed the readme.eml file that it uses as one of it's infection vectors and decoded the exploit.