W32.Rinbot!gen

Printer Friendly Page

Discovered: February 26, 2007
Updated: February 26, 2007 6:37:46 PM
Type: Worm
Systems Affected: Windows
CVE References: CVE-2006-3439 | CVE-2002-1145 | CVE-2006-2630

W32.Rinbot!gen is a generic detection for variants of the W32.Rinbot family. It performs various actions by connecting to a configurable IRC server and joining a specific channel to listen for instructions. It may also spread by exploiting certain vulnerabilities.

Antivirus Protection Dates

  • Initial Rapid Release version February 26, 2007
  • Latest Rapid Release version April 14, 2009 revision 056
  • Initial Daily Certified version February 26, 2007
  • Latest Daily Certified version February 26, 2007
  • Initial Weekly Certified release date February 28, 2007

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Mircea Ciubotariu

Discovered: February 26, 2007
Updated: February 26, 2007 6:37:46 PM
Type: Worm
Systems Affected: Windows
CVE References: CVE-2006-3439 | CVE-2002-1145 | CVE-2006-2630

Once executed, W32.Rinbot!gen variants may connect to a configurable IRC server, join a specific channel and listen for instructions to perfom various actions.

W32.Rinbot!gen may also spread by exploiting the following vulnerabilities:
Microsoft SQL Server 2000 or MSDE 2000 audit (Bugtraq ID 5980 )
Microsoft Windows Server Service Remote Buffer Overflow Vulnerability (Bugtraq ID 19409 )
Symantec Client Security and Symantec AntiVirus Elevation of Privilege (Bugtraq ID 18107 )

Recommendations

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

  • Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
  • Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
  • Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
  • Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
  • Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
  • Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
  • If a threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
  • Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services.
  • Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
  • Isolate compromised computers quickly to prevent threats from spreading further. Perform a forensic analysis and restore the computers using trusted media.
  • Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.
  • If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
  • For further information on the terms used in this document, please refer to the Security Response glossary.

Writeup By: Mircea Ciubotariu

Discovered: February 26, 2007
Updated: February 26, 2007 6:37:46 PM
Type: Worm
Systems Affected: Windows
CVE References: CVE-2006-3439 | CVE-2002-1145 | CVE-2006-2630

The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.

  1. Update the virus definitions.
  2. Run a full system scan.
  3. Submit the files to Symantec Security Response.

For specific details on each of these steps, read the following instructions.

1. To update the virus definitions
A generic detection can often occur if the antivirus program discovers a threat, but does not have the latest definitions. In these cases, you should download the latest definitions, then run the scan again.

The Intelligent Updater virus definitions are posted daily. You should download the definitions from the Symantec Security Response Web site and manually install them. To determine whether definitions for this threat are available by the Intelligent Updater, refer to the document: Virus Definitions (Intelligent Updater) . The latest Intelligent Updater virus definitions can be obtained here: Intelligent Updater virus definitions . For detailed instructions read the document: How to update virus definition files using the Intelligent Updater .

2. To scan for the infected files
  1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
  2. Run a full system scan.
  3. If the files previously detected as generic are now detected as another threat, please read the threats writeup for removal instructions.
  4. If the files are still detected as this generic threat, continue with the next step.

3. To submit the files to Symantec Security Response
Symantec Security Response suggests that you submit any files that are detected as generic to Symantec Security Response. For instructions on how to do this, read the following documents:

Writeup By: Mircea Ciubotariu