Saturday, 7 December 2013

Access Shared Folders Over Network: NetBios Attack

Hi friends!

Greetings!!

Today we are going to learn one of the primitive types of hacking: NetBios Attack.

Disclaimer: The below attack is for tutorial purpose and the blogger does not endorse the technique. Please note that if any thing (relating to this post or any other) goes awry, the blogger cannot be held responsible. This tutorial is only to show a potential attack of this type exist and all parties using computers should use preventive measures to be safe from this type of attack. The misuse of the tutorial can result in criminal charges brought against the person in question and the blogger cannot be held responsible in case anyone is misusing below information to break the law. This blog was created for information purpose only.

[I took more time to write Disclaimer than the tutorial]

What exactly it is: Well, If you are running a home network, chances are that you may have some folders, files or printer sharing turned on. With this attack, a hacker can get access to your shared resources over the network.

So lets see how it is done:

N.B.: I am using my own system for demo purpose.

#1: Find out the IP address of systems over your network(I have a separate tutorial lined up for this). For now arp -a could be used:






#2: Once you have the IP handy, let check if there is any shared files available on the system:


N.B.: 'A' is caps in the above command

#3: If there is no <20> under Remote column, then that system is not vulnerable to this attack. If there is, as in case of my system(see screen shot above), we can move to #4.

#4: Now its time to find out shared files over this system:


#5: We see that 4 files are shared over the network. Let's see how it can be accessed:




If all goes well, it will generally take 10-15 seconds to get a positive response

#6: Now opening the accessed folder in Explorer should be piece of cake for you:

That's all folks. You can watch videos on your local system as if it is your own system and not somewhere in the network.

Rest is Next
Cheers!

No comments:

Post a Comment