January 31st, 2003, 04:50 AM
I know you can telnet to SMTP, POP, IMAP, and FTP, send mail, download mail and download files with these services. I know this is a security concern and there are several ways to protect this from happening. I've also been told you can telnet to port 80 and do various things there. What I'm wondering what damage can an attacker do if they wear to gain unathorized access to this port, how would they do it and what you can do to prevent this. I've tried telnetting to a friends server(with his permission of course) on port and see if I could figure it out myself. Any input or further references to this subject would be greatly appreciated.
January 31st, 2003, 05:00 AM
If you are meaning port 80 (nomally HTTP), then none.
I'm wondering what damage can an attacker do if they wear to gain unathorized access to this port
They can find out what OS and web server you are using, unless it is masked.
Check out the tutorial by binary005 on "HTTP Basics".
is a firefox extension that gives you stats on how long you have quit smoking, how much money you\'ve saved, how much you haven\'t smoked and recent milestones. Very helpful for people who quit smoking and used to smoke at their computers... Helps out with the urges.
January 31st, 2003, 06:05 AM
the most used and most effective tool used against a web site is the web browser.
Bukhari:V3B48N826 “The Prophet said, ‘Isn’t the witness of a woman equal to half of that of a man?’ The women said, ‘Yes.’ He said, ‘This is because of the deficiency of a woman’s mind.’”
January 31st, 2003, 06:31 AM
Well, you have to understand that "telneting to a server/port" really only means that you are using a telnet client (an app that connects to a host on a specified port, and sends characters you input, to the remote host) to connect to a specific service.
This is nothing extra-ordinary. The only diffrence between "telneting" to a pop server and using a mail client to connect to it, is that you'll have to know the protocol/commands for that specific service.
That you send:
to a pop3 server by hand (in telnet) or in an automated manner (mail client) really dosen't make any diffrence to the pop server.
Same goes for http servers... Only diffrence is that YOU will have to work harder to get the same results.
Ok, yes, sometimes telnetting will give you more details, like http headers or banners that are usually hidden by client apps because un-interesting to the common user, but it's not like it's a "hack" in itself. That banner get's sent to your web browser anyways, it's just usually not showed to you.
Credit travels up, blame travels down -- The Boss
February 1st, 2003, 08:40 AM
Connecting to port 80 via telnet would enable you to send HTTP request, like your browser does and ppl have already said here. Only difference is that you can use it to get information through its methods, and sending malformed requests. But most of them might be done via browser, as tedob1 said. To get information about your sever (cgi vulnerablities), they may just use whisker, which is a tool that automates an otherwise quite boring process. You should just be aware of what kind of message reaches your webserver, not if they connected via telnet, netcat or Opera. Keep your servers up to date, and pay attention to your PHP files and CGI..
February 1st, 2003, 09:03 AM
Yeah, it's mostly uneffecting unless a user is trying to gain knowledge on what server your running (http) and what version, which could be used to help them to try to exploit your web server. Simply connecting to the site on port 80 isn't going to do much, nothing that (like others said) you can't do with a normal web browser. Just remember to always update your software (versions, patches, etc) and you should be fine.