Skip to main content

Insecure protocols

Some basic insecure protocols and risk associated with them:

FTP/Telnet/Rlogin/rsh/Rexec: These are insecure protocols because they use plain text authentication. This means that when you authenticate to the telnet or ftp server you send your login and password across the network un-encrypted or "in the clear". Data and even the password are transmitted as plain text. In addition to sending the login and password in the clear telnet and ftp also send the data or payload in the clear as well. There are commonly available programs that constantly monitor the network for packets that contains passwords. Preferably, all telnet and rlogin servers and clients should be removed from all machines.

Disable them if not used.

SNMP: Simple Network Management Protocol (SNMP) is a protocol for network management. SNMP lacks any authentication capabilities, which results in vulnerability to a variety of security threats. These include masquerading, modification of information, message sequence and timing modifications, and disclosure. Someone could receive SNMP traps from your machines and manage your network (e.g. bring up/down interfaces, disable packet filtering systems, etc.). Also, IIRC the community string and password are sent in cleartext; some basic packet sniffing could grab both pieces of information.

Disable it if not used .

SMTP-Open Relay: An open relay (sometimes called an insecure relay or a third-party relay) is an SMTP e-mail server that allows third-party relay of e-mail messages. By processing mail that is neither for nor from a local user, an open relay makes it possible for an unscrupulous sender to route large volumes of spam. In effect, the owner of the server -- who is typically unaware of the problem -- donates network and computer resources to the sender's purpose. In addition to the financial costs incurred when a spammer hijacks a server, an organization may also suffer system crashes, equipment damage, and loss of business.

Disable it if not used .

NFS: NFS is a client/server implementation that makes remote disks transparently available on a local client. It utilizes several daemons and configuration files to enable file sharing. By default, this process is all undertaken without any separate authentication, which makes NFS a security risk. NFS runs on the UDP protocol, which is a connectionless protocol because it does not require any acknowledgement of packet delivery.

Disable them if not used .

How to close FTP/SNMP/SMTP: Go to Control Panel-> Add/Remove Programs->Add/Remove Windows Components-

Select FTP and SMTP to disable them:

Select SNMP to disable it:

Disable NFS : Uncheck NFS in the list, if checked and click OK, Next to Finish:

How to disable Telnet: Go to Run->type “Services.msc”-> Look for Telnet in the list->Right click and select Stop:

I have just tried to compile all the issues at one place for easy reference.


Cindy Dy said…

I enjoy reading your articles. You really have a wonderful blogs. Keep up the good work. Thank you also for the information!

sarah lee said…
I really enjoyed reading your article. I found this as an informative and interesting post, so i think it is very useful and knowledgeable. I would like to thank you for the effort you have made in writing this article.

Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…