On October 26, 2000, Microsoft issued a press release confirming that its development unit was successfully penetrated by hackers. The development unit servers house the source code for Microsoft`s Windows and Office applications.
About the attack
Reliable sources assert that the system was penetrated using a worm called QAZ. The worm, first reported in China several months ago, is e-mail borne and has backdoor capabilities. This means that the worm initially appears as an attachment to an email, addressed to a user on the victim network. Once the attachment is executed, the worm splits into a two-part program. The first part of the program handles the replication of the worm, spreading through all shared drives on the network, searching for the directory containing the Windows "Notepad" application. Once the Notepad executable is found, the worm overwrites the executable with the second part of the worm`s program, which provides a "backdoor" to the affected network. This backdoor enables an unauthorized user to run specified files, to create new files on the victim machine, and to terminate the worm routines. When an unsuspecting user runs the infected version of Notepad, it establishes a connection to the outside world using port 7597. It also sends a notification to an address in China, containing the IP addresses of infected machines.
Microsoft says the attack originated in a Microsoft employee`s family computer, which may have been infected with the worm earlier. This may have provided passwords that allowed the attacker to access the corporate computers. The corporation says that according to network logs, the attack began on October 14th and lasted until October 25, and that the attackers had access to the source code repositories in the development unit for only a matter of minutes. Other sources indicated that the corporate security staff discovered the problem after detecting password files being sent to an email address in Russia.
Concerns Arising from the Attack
There were many concerns voiced about the impact of the attack on Microsoft and Microsoft customers, especially given the early suspicions that the attackers had accessed the source code for future Windows operating system versions and Office applications. Such access could allow attackers to modify operating system or applications code to enable attacks. It could also allow the attackers to analyze the code for unpublished security vulnerabilities, hence enabling attacks.
Considerable concern was also voiced that Microsoft would be vulnerable to such a well-publicized attack as the QAZ Trojan. Most commercial virus scanning products have signatures to detect and deal with the problem. This problem only serves to highlight the complexity of securing a large distributed corporate network. One security error in one computer system at the periphery of the network was sufficient to enable a major attack with devastating consequences.
What security measures would have helped and how?
Although this represents backseat driving at its finest, there are several lessons to be learned from this episode.
1. Although it is cheap, straightforward, and ubiquitous, virus scanning, with frequent update of detection signature databases, is extremely important. When possible, it`s advisable to back virus scanning with virus filtering, in which incoming messages are filtered for macro viruses.
NetCom Solutions SA provides our customers with best of breed Anti-Virus solutions from SOPHOS. SOPHOS specialises in the corporate market, thereby offering a value proposition suited to the corporate.
2. When one is responsible, as is Microsoft, for protecting source code repositories, it is wise to utilize a file integrity checker (such as Tripwire), generating signatures frequently, in order to be able to demonstrate that unauthorized changes were not made to products.
NetCom Solutions SA is the distributor for Tripwire in South Africa.
3. Good system logging and log review mechanisms (as are often provided by host-based and network-based intrusion detection systems) are absolutely essential when attempting to diagnose security attacks. They are especially important when trying to establish the exact footprint of an attack.
NetCom Solutions SA provides logging systems enabling this to be easily conducted. We supply a product called PRIVATE I from OpenSystems for this.
4. Early warning of abnormal patterns of system activity (as is often provided by intrusion detection systems) is helpful to those who wish to minimize damage due to attacks.
NetCom Solutions SA is the leader in IDS in South Africa and provides value added operational facilities as well. NetCom will monitor your network 24 x 7 for you.
5. Dependable, well-configured firewalls are essential for protecting networks. In the Microsoft scenario, such a firewall would have blocked the backdoor established by the worm (as port 7597 does not correspond to a standard network service.)
NetCom Solutions SA recommends the SolSoft NP network Policy tools for a corporate wide policy. This product allows a graphical interface to describe the policy, as you would draw it on a white board, then calculates the rules and propogates these to firewalls and routers with the capabilities. Results in a strongly implemented policy.
The role of tripwire in protecting against worm attacks
Tripwire (is a file integrity system, which uses cryptographic checksums to make critical files tamper-evident. This could have mitigated and minimized impact of the attack as follows:
1. At the initial point of attack (on the home computer system) - Tripwire (could have determined that the virus scanner signature file was not up to date, and notified system security personnel so that the signature file could have been updated.
2. At the initial point of attack, Tripwire (would have easily determined that the Notepad.exe file had been replaced with the Trojan Horse placed by the worm.
3. At the initial point of attack, Tripwire (would also have easily determined that the worm had altered the Windows registry.
4. At any of the subsequent systems attacked by the worm, Tripwire (would have easily determined (as above) the Trojan Horse replacement of the Windows Notepad and the alteration of the Windows registry.
5. In the development unit servers, Tripwire (would have made it far easier for examiners to determine whether unauthorized changes had been made to the source code.

