Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)
From: tcpdumb (tcpdumb_at_it-bytes.org)
Date: 07/27/03
- Previous message: Jason: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- In reply to: Justin Shin: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Maybe reply: Jennifer Bradley: "Re: Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Maybe reply: Jennifer Bradley: "Re: Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Reply: Nick FitzGerald: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: full-disclosure@lists.netsys.com Date: Sun, 27 Jul 2003 23:51:18 +0200
> However, a worm is N-E-V-E-R good and A-L-W-A-Y-S malicious. What would be the "good" intent of releasing any program that self-replicates to other vulnerable system and wreaks havoc?
Well that's not entirely accurate. At least RaMeN had some nice features such as fixing the security hole it used to gain access to the vulnerable Host. ;) (Even if it's just a feature to prevent multiple attacks, it's basically a good idea)
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
- Previous message: Jason: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- In reply to: Justin Shin: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Maybe reply: Jennifer Bradley: "Re: Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Maybe reply: Jennifer Bradley: "Re: Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Reply: Nick FitzGerald: "Re: [Full-Disclosure] DCOM RPC exploit (dcom.c)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]