Slashdot Mirror
Taming Conficker, the Easy Way
Dan Kaminsky writes "We may not know what the Conficker authors have in store for us on April 1st, but I doubt many network administrators want to find out. Maybe they don't have to: I've been working with the Honeynet Project'sTillmann Werner and Felix Leder, who have been digging into Conficker's profile on the network. What we've found is pretty cool: Conficker actually changes what Windows looks like on the network, and this change can be detected remotely, anonymously, and very, very quickly. You can literally ask a server if it's infected with Conficker, and it will give you an honest answer. Tillmann and Felix have their own proof of concept scanner, and with the help of Securosis' Rich Mogull and the multivendor Conficker Working Group, enterprise-class scanners should already be out from Tenable (Nessus), McAfee/Foundstone, nmap, ncircle, and Qualys. We figured this out on Friday, and got code put together for Monday. It's been one heck of a weekend."
If only the users who leave their printers unplugged habitually used linux...
To be fair, you can do something similar in Windows; but it sure isn't the soul of wit.
I've often wondered why Microsoft just doesn't implement some sort of security in Windows like other OS's have. It might prevent this kind of thing.
You mean like patching the flaw MONTHS before Conficker was released?
What having something like an application which could scan for it and remove it? You could call it "Malicious Software Removal Tool" and get it to run when automatic updates are done which would be handy. You could also allow users to run it themselves if they wanted by, say, clicking on Start, Run and typing in mrt...
Oh wait...
I only please one person per day. Today is not your day. Tomorrow isn't looking good either. - Scott Adams
You'll want to exclude at least /dev and /proc from that command if you want it to complete. I actually just prefer dd for ease of destruction.
Do you Gentoo!?
In fact, having double checked my information, the security patch that fixes the vulnerability that Conficker exploits was released prior to the creation and subsequent distribution of Conficker.
So, every single computer out there with a Conficker infection due to the exploit infection route could have been secured if patched. I would bet that would make for a gigantic reduction in the size of the Conficker botnet.
McAfee Stinger for Conficker located at: http://vil.nai.com/vil/averttools.aspx
(Hat tip to an AC comment at El Reg). Just a warning - it runs like a dog. I found that a passive Honeypot like Honeybot works well and is easier to install.
Never email donotemail@WeAreSpammers.com
There is no 'grand activation date'. April 1st *or later* when it updates itself.. it's more likely to upgrade to conficker D than do anything else.
It's just not in the authors interest to do any damage - whilst people don't know they are infected they can participate in the botnet. If the virus makes itself obvious then all that potential revenue is destroyed.
The f-secure blog puts it best: http://www.f-secure.com/weblog/archives/00001636.html
Pirated versions of Windows end up with automatic updating turned off as a way of getting around Microsoft's Genuine Advantage validation tests.
Because most viruses do not change the network behaviour of a host. Because most viruses are not visible from outside a host. Because this is a very rare case of a worm that actually changes the fingerprint of a host.
Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
So how do you use a mouse with a Scottish accent? Curious minds are dying to know.
http://www.youtube.com/watch?v=wzRziK-kZtQ
Just drop your geek card in the slot by the door as you leave.
I'd say as a rough guess, that 75% of viruses/trojans/malware nowadays turn off Windows Update as part of the infection process.
Somebody gets one of these fake Facebook spams, goes to the site in question to see Amanda Whatserface doing her striptease on stage, downloads Adobe_Player11.exe, so they can see the video, and bam. They're infected.
And before you bitch about them not having up to date antivirus.....I sent this file to virustotal.com a couple of days after I first got one of these spams, and it was detected as a known virus by a grand total of zero scanners.
Two flagged it as a suspicious file, and the rest (37 or so) let it sail on through.
Somebody gets hit with one of these things, and they'll have no A/V, no Auto Updates, and probably no firewall. They won't know it, because they'll also have no Security Center Service.
Or there's the possibility that they got infected, took their machine to a big-box moron to get it fixed, and the idiot in question cleaned the virus, but didn't enable all the disabled services. So again, no firewall, no Auto Updates.
It's not all because they're turned off intentionally.
"City hall" in German is "Rathaus" Kinda explains a few things......
Not in the UK, according to the articles that you linked to. The prosecution have to show that you intended to use the tool to commit a crime - possession is not enough. Did you actually read the links that you posted?
Yes, I did. According to the linked article, if you distribute a "hacker tool" that somebody else then uses for an illegal purpose, you're on the hook under UK law. Even if you commit no crime with it.
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
IIRC the actual standard has been reduced to 'could be useful to commit a crime'.
Several people in this country currently have criminal convictions for possessing certain books because they 'may be useful to someone planning a terrorist attack'
Not WERE planning attack. Not were part of a group of known terrorists with known events behind them. Just 'may be useful to someone planning a terrorist attack'.
Trust the law in this country? Hell no!
Assuming you are using BASH, enabling the shopt "dotglob" may be helpful if you want the * glob to expand to dot-files.
Colorless green Cthulhu waits dreaming furiously.
On the other hand, turning off system updates entirely is easy.
Yes, you go to Control Panel, Automatic Updates and click "Turn off Automatic Updates". Alternatively, you could click "Download updates for me, but let me choose when to install them", which is on the same dialog.
This is not a UI discovery problem.
dont admin windows much do you? you're right, you cant MANUALLY run updates, but the auto updates sure as hell get applied! wait... checking any of my 150 windows boxes running as user full time... yep! sure do!
You haven't been paying attention to the AV vendors for long have you? in 1997 McAfee merged with Network General and became Network Associates (nai.com) which also sold Sniffer. Then, in April 2004, McAfee became McAfee again when NAI tried to sell off the Sniffer product/Network General component (which was purchased by NetScout in November 2004). McAfee continued using the nai.com domain until June 30th of 2004, when archive.org shows nai.com redirecting to mcafee.com for the first time. vil.nai.com has been the Network Associates/McAfee Virus Information Library (and now the more generic "Threat Library") since at least 1999. (Incidentally, the "top 10 virus threats" in Oct 1999 included "Laroux", "Melissa" and "Happy99". My, how far we've come....)
Looks to me like you just use the smb checker script. If you have the latest source from SVN, omething like this should work:
nmap -sS --script smb-check-vulns.nse -p 139,445 -v -d -P0 -oA outputfilename hostornetworktoscan
Hey guys,
I'm the author of that script, and that's exactly right. I posted a full explanation on my blog.
http://www.skullsecurity.org/blog/
WARNING: These checks are dangerous, and are very likely to bring down a server. These should not be run in a production environment unless you (and, more importantly, the business) understand the risks!
As a system administrator, performing these kinds of checks is crucial, because a lot more damage can be done by a worm or a hacker using this vulnerability than by a scanner. Penetration testers, on the other hand, might not want to use this script -- crashing services is not generally a good way of sneaking through a network.
If you set the script parameter 'unsafe', then scripts will run that are almost (or totally) guaranteed to crash a vulnerable system; do NOT specify unsafe in a production environment! And that isn't to say that non-unsafe scripts will not crash a system, they're just less likely to.
MS08-067 -- Checks if a host is vulnerable to MS08-067, a Windows RPC vulnerability that can allow remote code execution. Checking for MS08-067 is very dangerous, as the check is likely to crash systems. On a fairly wide scan conducted by Brandon Enright, we determined that on average, a vulnerable system is more likely to crash than to survive the check. Out of 82 vulnerable systems, 52 crashed.
Bow before me, for I am root.
Automatic updates runs as a system service under the local system account so your computer will automatically receive and install automatic updates even if your login has only restricted rights.
Unless you turn on this option in your group policy:
Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update -> Allow non-administrators to receive update notifications.
Set it to enabled and then even your limited users will be able to see that they have updates to install.
That's correct. I added a 'safe' parameter last night, since the Connficker check is safe, and have been advocating its use in all my posts (you'll see "script-args=safe=1" in everything). Watch out for that.
And for what it's worth, even if 'safe' is missing, it's only going to crash stuff that isn't patched for MS08-067.
http://www.skullsecurity.org/blog/
The -f will skip over anything that can't be done, you know.
/dev? I'll answer that for you: No more deleted files. Everything prior to it getting to /dev is gone, but the rest is left. By going directly to the device with DD you'll complete the overwrite.
What happens when your HD node is deleted from
Do you Gentoo!?
nmap -PN -T4 -p139,445 -n -v --script=smb-check-vulns --script-args safe=1 [targetnetworks]
For more details, see the announcement at http://insecure.org.
-Fyodor