 Originally Posted by Mes Tarrant
Ok, googled Conficker and here's a quote from the first link that popped up (unrelated to whether or not it's a joke, but still important):
Microsoft issued a software update that protects computers from Conficker in October. Most anti-virus software will also stop it. The result is that while Conficker is spreading rapidly, it is mainly doing so in parts of the world where people haven’t updated their systems. About 29% of infections are in China, followed by Argentina, Brazil, Russia, and India, according to Symantec. Many of these countries are among those with the highest rate of software piracy, which probably isn’t a coincidence. Less than 1% of infections appear to be in the U.S. according to multiple security researchers.
with all due respect, it's a lot more complicated than just updating windows....
Conficker has had half-a-dozen variants and it is remotely updatable
The MS update in October 2008 patched against Conficker A
Bob gets infected (windows not patched)
Bill doesn't get infected (windows patched)
Bob's Conficker is remotely updated with a new attack vector
Bob infects Bill using the new attack vector
The newest variant of Conficker, C, was only launched on the 4th of March - that's less than a month ago
Here's a full analysis of Conficker C
http://mtc.sri.com/Conficker/addendumC/
This is going to be big
*edit*
Some nice quotes from the above analysis
Finally, we must also acknowledge the multiple skill sets that are revealed within the evolving design and implementation of Conficker. Those responsible for this outbreak have demonstrated Internet-wide programming skills, advanced cryptographic skills, custom dual-layer code packing and code obfuscation skills, and in-depth knowledge of Windows internals and security products. They are among the first to introduce the Internet rendezvous point scheme, and have now integrated a sophisticated P2P protocol that does not require an embedded peer list. They have continually seeded the Internet with new MD5 variants, and have adapted their code base to address the latest attempts to thwart Conficker. They have infiltrated government sites, military networks, home PCs, critical infrastructure, small networks, and universities, around the world. Perhaps an even greater threat than what they have done so far, is what they have learned and what they will build next.
Like Conficker B, C incorporates logic to defend itself from security products that would otherwise attempt to detect and remove it. C spawns a security product disablement thread. This thread disables critical host security services, such as Windows defender, as well as Windows services that deliver security patches and software updates. These changes effectively prevent the victim host from receiving automated software updates. The thread disables security update notifications and deactivates safeboot mode as a future reboot option. This first thread then spawns a new security process termination thread, which continually monitors for and kills processes whose names match a blacklisted set of 23 security products, hot fixes, and security diagnosis tools.
Conficker C incorporates a variety of strategies to secure and defend its installation on the victim host. To do this, C employs several measures to cloak its presence, as well as measures to kill or disable security products that would otherwise detect its presence. C's assault on security products begins right away, just after its mutex checks (to detect new installs from reinfections). At each process initialization, it performs an in-memory patch of the host's DNS resolution services to prevent domain lookups to a variety of security product (and research) sites. C then spawns a separate thread to halt and disable security and update services, and then enters an infinite loop. There, it continually searches for and terminates active security products and patches. These steps are performed each time C is invoked.
Upon first installation, C installs itself and obfuscates its presence on the victim's host,. These steps allow it to avoid easy diagnosis and removal by an attentive user. It deletes all restore points prior to its infection to thwart rollback, and sets NTFS file permissions on its stored file image to prevent write and delete privileges. Most of this logic also appeared in prior version, but here we find some extensions and updates.
C also incorporates logic to disable Windows' firewall protection of certain high-order UDP and TCP ports. These firewall adjustments are not performed at initialization, but rather occur when C enters its network communication logic.
|
|
Bookmarks