Using Honeypots to Fight Worms 229
scubacuda writes "Laurent Oudout, an active member of the French Honeynet Project (part of the Honeynet Alliance), has written a paper evaluating the usefulness of using honeypots in fighting Internet worms. (Imagine a well-constructed honeypot framework capturing a worm, redirecting worm traffic to fake services, and launching counter attacks to clean infected hosts!)"
Honeypot for lawyers (Score:4, Insightful)
Re:Honeypot for lawyers (Score:2)
Re:Honeypot for lawyers (Score:3, Informative)
1) Shooting is only justified if you feel your life is in danger and you are incapable of running away. Pretty arguable point when the attacker is only weilding a bat.
2) Unless your Iron Lung is hooked to the internet, no internet attack is an attack on your life. If I steal your laptop from your tru
Re:Honeypot for lawyers (Score:3, Insightful)
In addition, that scenario is flawed. In the theft scenario, the crime is already complete, and what is being done is revenge (which is wrong). I think both of us have flawed analogies. A more accurate representation would be if somebody was breaking into my house, and I hit them with a fucking brick to make them stop.
Re:Honeypot for lawyers (Score:2)
Re:Honeypot for lawyers (Score:2)
Try googling on the guys name. Or louisiana halloween shooting japanese
Re:Honeypot for lawyers (Score:3, Informative)
Mostly wrong. For example, in the jurisdiction of New York, see this page [cornell.edu], or Google yourself. Quote:
Running away from a guy beating you with a bat is not "complete safety". You would
Honeypot (Score:5, Interesting)
If a user is infected and randomly attacks IPs within our network, they eventually hit one of the honeypots. The honeypots flag their account and when they next reconnected they are sent to a 'walled garden' - a dummy DNS RADIUS community where they can only get one webpage, that advises them that they have a virus and provides a download section for removal tools. When they have downloaded all necessary patches, they are automatically removed from the walled garden (using apache logs and RADIUS trace IPs to link the download with their account) and allowed back on the network.
There's no legal issues involved with us - we are a residential ISP and stuff like this is covered in T&Cs.
Re:Honeypot (Score:2)
WOW. I like that. I like that a lot. This should be standard practice. It's not invasive at all, and it forces the schmucks who never paid attention when they got their massively powerful infection node^W^Wcomputer to finally get up to date.
Let's face it, as long as we have uneducated users, these problems will continue to crop up. If we can keep them offline until they learn the simplest parts of system maintenance, then maybe these problems wo
Re:Honeypot (Score:2, Insightful)
So as long as I get my prescription filled, you'll let me out of quarantine? Great! I don't actually have to take my antibiotics, as long as they're nearby.
Re:Honeypot (Score:2, Insightful)
Re:Honeypot for lawyers (Score:3, Informative)
Re:Honeypot for lawyers (Score:2)
Re:Honeypot for lawyers (Score:3, Informative)
It is kind of like leaving your car doors unlocked in the middle of NYC and pointing a video camera at it to see who tries to steal it.
Attractive Nuisance (Score:2, Insightful)
Re:Honeypot for lawyers (Score:3, Insightful)
Get a clue! If the honeypot system is trying to knock out your computer, you've already been hacked!!! Your computer has gone rogue! In fact, it's almost as bad as the dog jumping the fence and mauling people!
And don't give that sorry excuse: "so two wrongs make a right, eh?" That's no way to run the internet! The internet is supposed to attempt to fix itself when things break.
Re:Honeypot for lawyers (Score:2)
Sorry, that is just as wrong and illegal. Getting the infected comp yanked of the net is one thing but making unauthorized changes, what-ever your intent is just as bad as the original person who spread the virus. Now if say your ISP were to have you sign an agreement giving them the right to preserve the network stability by making local host changes, you would be covered, and MORE POWER TO YA, but as it stands now most ISP's have only one recourse and tha
Vigilantes or Revolutionaries? (Score:2)
This may be a bad precedent (and illegal), but without any effective legal methods to stop the 'bad guys', it's essentially all we've got. This is a full assault - hackers, crackers, script-kiddies, scammers, spammers, etc. are not holding back, they're not stopping, and they've got little resistance. Legal methods (anti-viral programs, patches) aren't doing much to stop them - it's not a war, i
The owner of a computer (Score:2)
Counter attacks don't work (Score:4, Insightful)
Re:Counter attacks don't work (Score:2)
I'm still waiting for Jan. 1st, 2004.
Re:Counter attacks don't work (Score:5, Interesting)
Re:Counter attacks don't work (Score:3, Interesting)
Unfortunately, what is reasonable and what is legal are not always the same thing. Anyone considering embarking on such a project would be very well advised to consult with a lawyer before getting too far into it.
Re:Counter attacks don't work (Score:2)
Then the law needs to be revised - a definition of "an active, compromised machine" worked out, and a provision for designated organisations to be empowered to react to attacks from such compromised machines in such a way as to prevent the attacks. Whether this is patching the machine or crashing it, I really don't mind. Do IP blocks have email contact info associated with them in a similar way to domains?
Re:Counter attacks don't work (Score:3, Interesting)
When you have hackers using automated systems, remote controlled computers, etc, to do their hacking for them, we will eventually reach a point where we, too, will need to use automation to fight them.
This is the exact same pattern you see in every other area where automation is now being used: nuclear power, jet aircraft, etc.
Re:Counter attacks don't work (Score:2)
I will cheer just as loudly when the makers of "benevolent worms"
Re:Counter attacks don't work (Score:2)
Completely overlooking the fact that the response is to alter a system that is not under your control without the owner's permission. You can block at the router if you want, thereby denying traffic from the host, but I would argue that making alterations to another's system without permission is exactly as unethical (and probably illegal, depending on jurisdiction) as the original worm.
Re:Counter attacks don't work (Score:5, Interesting)
However, as another poster said, it's a lawsuit waiting to happen. Even if the project were technically successful, some schmoe out there would try to abuse it somehow.
Re:Counter attacks don't work (Score:3, Insightful)
Re:Counter attacks don't work (Score:3, Insightful)
Although decidedly risky legally-speaking, it would mean that only vulnerable hosts would get contacted and have fixes forcably deployed on them -- meaning that as the original infection dies down then so too will the number of forced deployments.
The key problem with the Welchia worm is that it simply didn't go away. It continues to actively probe and scan for vulnerable machines indefinitely -- an
Re:Counter attacks don't work (Score:2, Informative)
This script, given strictly as an example, can be improved upon by using evolved programming languages such as VBS. A longer example [ref 13] has been tested on a research network, cleaning our infected hosts in a few minutes.
Some SysAdmins were recently polled to determine if it is ethical to take active defense measures in such a targeted, counter offen
Re:Counter attacks don't work (Score:2, Insightful)
Re:Counter attacks don't work (Score:2)
Re:Counter attacks don't work (Score:2)
Re:Counter attacks don't work (Score:3, Insightful)
Worms too?! (Score:4, Funny)
Re:Worms too?! (Score:2)
Comment removed (Score:4, Interesting)
Re:Clean infected hosts? (Score:2)
I assert my right to self-defense. You attack me, I'll attack you in exactly the same way (you see, I already know you're vulnerable to that exploit), and shut you down so you can't continue to attack. I won't wipe you or patch you or do any permanent damage.
"you" and "me" can be either we as persons or our respective servers. It doesn't matter technically, so I fail to see why it should matter legally.
That said, I practice what I preach. I've had a
not really (Score:2)
Re:Clean infected hosts? (Score:2)
If shutting your machine down is the minimum required to prevent future attacks on me and others (yes, almost all self-defense laws do include not only defending yourself, but also defending others), then that is exactly my point.
I could firewall myself. But that wouldn't prevent you from attacking others. It also wouldn't stop further attacks on me - it'd just make them inconsequential. However, they are still occuring. Just because your blows don't hurt me doesn't me
Re:Clean infected hosts? (Score:2)
If attacks persist from a host after a month, then perhaps a flag for an automatic response would be appropriate
Even better (Score:2, Interesting)
Skynet! (Score:2, Funny)
Yeah, the honeypot could proactively install patches to systems that it deemed infected, all around the world!
Sounds like Skynet. Run for the hills!
Reminds me of what AOL did (Score:5, Interesting)
Still what can one do against users who do not care if they have a worm or not? Should we invet a driving-license thing for the internet, with fines for disregarding the rules? But then we would have the "internet must stay free"-activists on it again
Personally I'd vote for some sort of internet driving license, without having thought much about it. But it feels like the right thing.
Oh well, babbled enough, back to work
Re:Reminds me of what AOL did (Score:2)
a) discourage new users
b) make people afraid to try new things online
c) create some kind of institution with an incredible amount of unwarranted power
Re:Reminds me of what AOL did (Score:2)
It has not been much of a problem in
Re:Reminds me of what AOL did (Score:2)
Well, you are of course right. It would definitely reduce some of the "freedom" the internet users. But to keep the driving-license analogy, what would happen if no driving license would be needed and driving would generally be without any rules? It would be a similar situation as the one we have now on the internet, there would be some/many people who are rational and intelligent enough to do things right intuitively, but there would also be people who just do not care.
Yeah, they're perfectly similar, e
Re:Reminds me of what AOL did (Score:2, Insightful)
Re:Reminds me of what AOL did (Score:2)
Yea, because people who can't handle a simple patch procedure are going to understand the subtle stupidity of Windows Messenger. I can see my e-mail now...
OMG! I'VE BEEN HACKED! lol!!! OM!G JIT SAYS SOMETHIGN ABOUT WORMS YOU HAVE TO COME FIX MY COMPUTER I DONT KNOW WHAT'S WRONG! LOL!!!!
Attachment: "Latest Windows Security Update.exe"
Re:Reminds me of what AOL did (Score:2)
Personally I'd vote for some sort of internet driving license, without having thought much about it. But it feels like the right thing.
Nice idea, but I was thinking of something more along the lines of a bat. You could put big letters on the side "CLUE"
Re:Reminds me of what AOL did (Score:2)
To make it worthwhile, people would be required to type in their I.D.L. # to use a computer, destroying the entire concept of privacy.
Re:Reminds me of what AOL did (Score:2)
Uh.. yea... because it's not like we have anything that can be used to track us now. Like IP addresses cross referenced to logfiles. Nope, nothing like that around anywhere.
Re:Reminds me of what AOL did (Score:2)
The conter-attacks to patch infected machines are a bad idea, most certainly illegal.
Re:Reminds me of what AOL did (Score:3, Insightful)
I'm all for privacy and anonymity, but when 1 anonymous person has the potential to introduce a virus that can bring down a corporation's network (or neighborhood's broadband access) through sheer negligence, I very strongly start to question the limits of that privacy.
Of course, a fantastic solution to the problem would be software that doesn't have 59,000 exploits and so many features
Re:Reminds me of what AOL did (Score:2, Informative)
Re:Reminds me of what AOL did (Score:2)
Re:Reminds me of what AOL did (Score:2)
idiocy (Score:5, Insightful)
I don't think worm writers are going to care very much. If they're spammers, then some more of their spam will go in the bin - but it's not costing them, so who cares?
On top of this you are definitely on crack if you think that "launching counter attacks to clean infected hosts!" is a) a good idea or b) legal.
Re:idiocy (Score:4, Interesting)
I understand where you're coming from, but let's take an analogy : in any other walk of life, if you are attacked you are allowed to take reasonable actions to defend yourself.
If someone comes at you and other people in the street with a knife, you are allowed to wrestle the knife from him. Things such as punching him, pinning him or even breaking his arm might be viewed as perfectly reasonable by a judge - in order to prevent harm.
In the same vein, we're talking about disarming the offensive person (host) without causing any collateral damage... So why might this not be considered legal by an enlightened society?
Re:idiocy (Score:2)
More accurately, you're not allowed to key the car of someone who just keyed your car, which is what attacking an attacking computer would be more like.
It seems to me that the main problem with most worms that we've seen so far is the havoc they wreak on the network as a whole, chewing up bandwidth as they propagate, rather than what they do to the machines in question. How would a "good" worm be any different? It has to propagate by the s
yeah, this is a waste. (Score:2)
There's nothing wrong with trying to clean up your own network. These boxes would be a great idea on a corporate network. When some new M$ transmitted disease comes springing out of LookOut of Internet Exploder, a central box could fix the problem.
For all that, I still think projects like this are a waste of time. Why should prople spend their time fixing Windoze? The best you can hope for is the RAV fate, a buyout. Microsoft m
Re:idiocy (Score:2, Funny)
What if it's a tool that you have deployed in your network, and it just so happens that the honeypot is a little bit misconfigured, allowing it to respond to all hosts that attempt to infect it?
How is this then different from desktops that are poorly written/designed or misconfigured allowing them to spread viruses on the internet?
The purpose of the tool (vir
Smokey the Bear says... (Score:3, Funny)
Surround your honeypot with rocks to keep the fire from spreading. Be sure when
you're done with your honeypot to put it out with a bucket of water and make
sure it has stopped smoking before you leave the area.
Remember what Smokey the Bear says. Only you can prevent your honeypot from starting a forest fire.
Re:Smokey the Bear says... (Score:2)
Yes, build a firewall.
Bad Idea (Score:5, Insightful)
They're just that, 'attacks.' Unauthorized access to users' machines with the intent of installing software without the users' knowledge (even with, it makes no difference.)
It's a nice idea in spirit, the Community (I hate that term) working to automatically protect those who can't help themselves (sounds rather elitist, doesn't it). But in the end, it's no better than your average hacker / skript kiddie futzing around with your machines.
Re:Bad Idea (Score:2)
If someone is randomly assaulting people in the street, should you just run away and lock yourself up at home, or should y
legal way to have internet connection shutoff (Score:5, Insightful)
Re:legal way to have internet connection shutoff (Score:2)
This happened to me. (well, no court order or what not). My ISP monitors for network anomolies, and thought that I had welchia (I had actually ran a portscan against one of my servers). They put a flag on my account, and disconnected me, and waited for me to call them to find out what happened.
What would be a good solution, is some kind of 'secure' winpopup. (ie, mabey an ISP gives you a public key, that your machine will accept messages from) ISPs could then give their users notice of suspected activi
Re:legal way to have internet connection shutoff (Score:2)
Automatic firewall definition update (Score:2)
It is obvious that 'attacks' can ony be made inside a corporate network or similar, or else one would probably face lega consequences.
Apart from that, I think this is a great idea. You could use honeypots to automaticly update firewall filters and block further infection attempts!
Re:Automatic firewall definition update (Score:2)
Re:Automatic firewall definition update (Score:3, Insightful)
Good luck. Name me one product you'd trust to automatically adjust your perimeter security.
I nearly wet myself laughing when I first saw ISS present their ideas of reactive firewall configuration based on IDS alerts. There are a number of serious issues with this school of thinking, understandable though the initial logic may be.
First off, there is currently no single piece of software in existence smart enough to intelligently distinguish malicious traffic with a high enough degree of reliability to tr
Know your enemy (Score:4, Insightful)
Just having a honeypot that can alarm us to what boxes are infected is a big plus. We can take it from there.
Somehow taking the computer off the network would be a bonus as well. I wish our firewall had this functionality.
Nice try (with fixed link) (Score:5, Insightful)
Unfortunately for him, I have just published a paper [lemuria.org] that shows that and how future worms will be much too fast for his - or anyone elses - manual defense methods.
In short, I've demonstrated that by the time he's starting to analyze the worm, it has already infected 90%+ of the vulnerable machines.
As soon as worm writers acquire some coding skills (most of the past worms were pathetic), all defenses that require manual actions will be too slow.
Sorry.
Re:Nice try (with fixed link) (Score:2)
You might want to have a look at Nick Weaver's Homepage [berkeley.edu]--How to 0wn the Internet in your Spare Time is a pretty good approach to this as well.
Frankly, you're correct in your assumption. However, the author makes a good start in terms of preventing that initial spread. I agree that if you focus too much on 'reaction', dependent on identification of a worm, you're screwed to start out with. But there are several schools of thought related to detecting anomalous traffic and, for example, shutting it off at
Re:Nice try (with fixed link) (Score:3, Interesting)
I've read that one, and it is referenced in my paper.
However, the author makes a good start in terms of preventing that initial spread.
Chapter 4.5.1 of my paper shows how to circumvent that questionabe protection.
But there are several schools of thought related to detecting anomalous traffic and, for example, shutting it off at source, or automatically rate limiting it.
That is the correct approach. Until worms
Re:Nice try (with fixed link) (Score:2)
I honestly had just scanned over your paper, but I will read it in detail asap.
I don't doubt you at all. In fact, I am happy for yet another legitimate-looking piece of work which says this. In fact, this statement is one of the cornerstones of all the security incident response mechanisms and structures we've been putting together in my current project. You're preaching to the choir
Nice try indeed - an internet immune system! :-) (Score:2, Interesting)
If you actively update the "defense boxes" with all the latest exploits and then configure it to use it's full arsenal to take down any attacking hosts (e.g. by making all exploits simply turn off networking on the target machine), then you'll have a very high success rate indeed. Then only worms exploiting previously unknown holes on otherwise fully patched machines will be able to run unchecked. This raises the bar for worm writer
Your TeX has a few typos (Score:2)
t = \log_{(r+1)} n_t - \log_{(r+1)} i
Not, as you have there,
t = log_{(r+1)} n_t
Actually, this does slightly modify your results (Score:2)
I will concede that this point isn't crucial, however. It still makes a worm that hits saturation in under a minute very close to ideal.
Re:Actually, this does slightly modify your result (Score:2)
There has been much feedback from the community ever since I posted it, and I will update it soon (have a conference talk to do that takes priority right now).
Re:the Counterstrike phase will nullify your paper (Score:2)
Yes, imagine that.. (Score:5, Informative)
fascinating article.. (Score:3, Interesting)
If a host had the latest patches applied, wouldn't it be immune from attack? Didn't MS release the patch for the RPC exploit months before the virus came out? I think it would be better to have a small network of 6-8 computers (wouldn't have to be much, just get a rack off Ebay and a few of those mini-itx components, load em in, don't need a fan, case, etc) and have each computer at varying levels of patches. One computer is patched every day, one patched every two weeks, etc. There isn't enough time to customize a computer to be infected by the worm; by the time you hear about it, the worm has already infested millions of computers.
They also should look more into that counterstrike idea. Seriously, if you attack my computer, even if you didn't know about the virus, then I have the right to self defense. I'll gladly install some of that counterstrike software when I set up a honeypot. You're PO'ed because I attacked your computer? You attacked me first. I'm only exploiting the same vulnerability the worm did. If you were a SMART web citizen, you would have gotten a firewall to protect yourself from the worm in the first place.
Re:fascinating article.. (Score:2)
Assuming that MS the infallible (random quote..."No one would ever need more than 640K") identifies EVERY flaw BEFORE worm writers do than yes, patching makes perfection. Please, do not assume that.
How about using honeypots to attack back?! (Score:2)
Or, for virus writers, how about giving them a good dose of SARS or AIDS?? That'll teach them to play games..
Good article (Score:5, Informative)
For active countermeasure (or attack), this has to be done VERY carefully. Remember Max Vision? It's good to fix your own machines, and make sure you only attack and fix yours. Access to unauthorized machines are almost always illegal. If one of your boxes got hacked, the incident response team should get involved and do their investigation, auto-patching without investigation can be a risky thing because you just don't know the extend of the problem. When you fix it, the hacker could have backdoor installed on your box.
Yeah... (Score:3, Interesting)
Legal implications of counter-attack? NOT! (Score:3, Insightful)
Before I had a webserver up-n-running doing useful stuff, I had Code Red Vigilante [crazybob.org] running on port 80; it felt good knowing that machines that had tried to infect me were being warned that they were infected... you know, trying to be a good netizen and enlighten my fellow surfer.
Of course, I was able to do that because I could look through the Java code I was installing and determine exactly what that code was doing (ie, not fall victim to a socially engineered attack where I mistakenly INSTALL someone's worm code on my computer!)
No... the real question won't be how this all gets sorted out legally; we'll figure out how to use technology to stop this crap before any law gets passed to "protect me."
The real question will be how do we protect the average person in the interim without making them easily exploitable targets for malicious anti-worm code that is, in essence, a socially-engineered worm attack in its own right.
Re:Legal implications of counter-attack? NOT! (Score:2)
The Solution is IPv6 (Score:2)
But the problem of scanning the IPv6 space is non-trivial. Not only is it easier to hide somewhere inside this much larger space, but serious folks, why don't we start from the beginning having routers to identify obvious scanning attempts (i.e. requests to a whole lot of di
Sounds AWFUL (Score:2)
As a matter of a fact it sounds an awful lot like the anti-blast worm some jackass wrote. That bit of well meaning cyber-carpentry got on my network despite being prepared for blast and it did very similar damage. The honey pot project should look for useful things to the community not to an individual.
Contract "passive" honeypot vs "active" scanner (Score:2)
The key difference here is that the honeypot is passive, it does not go out looking for vulnerable hosts, it waits until after the three-way TCP handshake on TCP/135 is complete, and only then does it r
How I dealt with Welchia (Score:3, Informative)
My solution was to deploy honeypot windows machines running snort which reported into a central SQL server database.
Using Windows scripting host, I then wrote a script that ran periodically on a network management workstation which queried the database, creamed off the last machine that was an infector and using the wonderful free PS Tools [sysinternals.com] from Sysinternals [sysinternals.com] automatically determined what OS the machine was running (PSInfo), updated its antivirus signatures (PSExec), de-wormed the machine using the Symantec "FixWelch" [symantec.com] utility (again using PSExec), decided if the machine was up to service pack spec (data from PSInfo) and if not service packed it (PSExec) then applyed the patches to prevent re-infection (PSExec).
All worked a treat.
I'm kind of glad we got hit because as a result I can now insist machines get patched (previously people would complain about a "box on the screen" (SMS installer)) while also being able to remove machine admin rights across the board and ban any machines that are not ours from being connected on pain of a disciplinary offence.
A lot of work but ultimately, I WIN. MOO HAR HAR!!
LaBrea extended (Score:2, Informative)
Re:Legalaties (Score:2)
Even if this eventually is used (and I hope to God it's not) there would have to be all kinds of of legislation defining "good" worm and "bad" worms.
Can you imagine the government sitting aournd trying to do this?
Also, who decides what is removed? What's to keep someone from saying, "downloading mp3s is illegal, we are going to write a "good" worm to remove mp3s without drm?" Sure
Re:Legalaties (Score:2)
Launching a counter-worm is obviously a bad idea, but I see nothing wrong with disabling the original worm on any system that tries to infect the honeypot.
I did some experiments along those lines, with Apache set up to redirect various common worm-generated requests to a CGI which tried to do a "dir" on the remote system using the same hole that it was using to try to get my system, and a large fraction of the time, that worked.
On some of thes
Re:Nice try (Score:2)
Re:Important Question (Score:2)
Sort of. Same basic concept. Write a program and use some of their secret copyrighted comments. Here is a good example of a way to cause SCO to own you (C Code excerpt):
\\This is broke. Fix it later
That comment is obviously part of Sys V Unix