Spawning Reverse Shell Anytime With Any IP

24 Pages·2012·3.07 MB·English

SSppaawwnniinngg RReevveerrssee SShheellll
AAnnyyttiimmee WWiitthh AAnnyy IIPP !!
BBhhaauummiikk MMeerrcchhaanntt
Author And Speaker at….
Objectives
•
Reverse shell basics
•
Advance reverse shell method
•
Dynamic DNS concepts
•
Demo
Let’s Consider One Scenario To
Understand Reverse Shell Attack……
•
Jack works in a corporate environment which is protected by
IPSs , IDSs , Firewalls etc.
•
He plans for an attack , and decides to plant reverse shell ,
because few security mechanisms permit some amount of out
bound traffic.
•
He wants to spawn the shell from his office machine to home
machine after 6 p.m, i.e. once he reaches his home.
•
Jack wants one live system which is up and going,
plus a handler running on it at his place, to receive
the shell.
•
Jack must know the IP address of his home machine
before planting the shell in the office machine.
Then what is the roadblock for Jack?
•
Jack’s home machine should be working during the
office hours with the handler listening on some port
to get the shell .
•
Jack should know the IP address of his home machine
before planting the shell into office machine.
•
But if he is using PPP or DHCP mechanism then IP
address will change for each connect and disconnect.
(ISPs allocates Dynamic IP to home users, e.g. Home
Routers , Internet Dongles)
What Is The Original Problem In Following
The Formal Way To Spawn Reverse-Shell?
•
Your Place
•
Your Time
•
Your IP
#include < reverse-shell.h>
• Handler started in the attacker machine.
One
• Payload transfer phase from attacker to victim
machine.
Two
• Reverse Shell or msf payload injected in the victim’s
machine.
Three
• Attacker get’s victim’s bash/cmd (Attack !! )
Four