Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Full-disclosure] .NET REMOTING on port 31337 |
|---|---|
| Date: | Fri, 28 Sep 2007 13:38:17 -0500 |
I disagree, don't block access to the port. Monitor and capture it. Joel's First rule of forensics: Don't just do something, stand there! Watch it, monitor it. If it is a crafty backdoor, there are dozens of others to enable bad guys to regain entry. Blocking lets the hacker know you might be on to them. IF it is legit, then it could cause a problem. Telnet to the port, see what it says on connection; run fport or sysinternals utilities on the box to see the stack the program uses. -joel From: full-disclosure-bounces@lists.grok.org.uk [mailto:full-disclosure-bounces@lists.grok.org.uk] On Behalf Of Fabrizio Sent: Friday, September 28, 2007 1:31 PM To: Full-Disclosure Subject: Re: [Full-disclosure] .NET REMOTING on port 31337 If you think it's that critical, (i think it's that critical) start by blocking any connections from anywhere to that machine/port. See if anyone complains. Check any old firewall logs for that port while you're at it. Then continue your investigation!! Fabrizio On 9/28/07, Simon Smith <simon@snosoft.com> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Got output... and it was... no idea what it was... can't paste it due to confidentiality though. Fabrizio wrote:
.NET Remoting is "a generic system for different applications to use to communicate with one another." It's part of the .NET framework, obviously. (not trying to be a smart ass) I'm gonna take a wild guess and say it's not a good thing...... Connect to it, and see if you get any output, if you haven't already done so. Fabrizio On 9/28/07, * Simon Smith* < <mailto:simon@snosoft.com> simon@snosoft.com <mailto:simon@snosoft.com>> wrote: Has anyone ever heard of .NET REMOTING running on port 31337? If so, have you ever seen it "legitimate"?
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html <http://lists.grok.org.uk/full-disclosure-charter.html> Hosted and sponsored by Secunia - http://secunia.com/
------------------------------------------------------------------------
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
- -- - - simon - ---------------------- http://www.snosoft.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG/UY+f3Elv1PhzXgRAs/BAJ42Vwk5+cvWfoYo4wUl74LDnUtz7wCgzW9s O/+SDoZYgZ1r1oDjKpKzZIo= =n54j -----END PGP SIGNATURE-----
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
| Previous by Date: | Re: [Full-disclosure] .NET REMOTING on port 31337, full-disclosure |
|---|---|
| Next by Date: | Re: [Full-disclosure] .NET REMOTING on port 31337, full-disclosure |
| Previous by Thread: | Re: [Full-disclosure] .NET REMOTING on port 31337, Simon Smith |
| Next by Thread: | Re: [Full-disclosure] .NET REMOTING on port 31337, Fabrizio |
| Indexes: | [Date] [Thread] [Top] [All Lists] |