‫The browser exploitation framework, also known as beef, is a penetration testing tool that focuses
‫on the web browser amid growing concerns about web born attacks against clients.
‫Beef allows ethical hackers to assess the actual security posture of a target environment by using client
‫side attack vectors, so let's use the beef framework with stored excess.
‫Let's go to Carly, run Firefox and connect OWASP broken Web application using its IP address, or if
‫you defined like me using the domain address and click the -- vulnerable web application, log into
‫the application using admin, admin or user user credential, click excess stored link.
‫Now, we already know that this page includes stored excess vulnerability.
‫Let's see it again rapidly.
‫Now I go to my host machine, which is a Mac, open a browser and connect to a Wasp broken web application.
‫Now, because the domain name is not included into the host file of my host machine, I connect to the
‫application with its IP address this time and click -- Vulnerable Web Application Link.
‫When I click excess stored link as it's supposed to be, the script embedded by the collar user runs,
‫this is the nature of this stored excesses.
‫Go to the home page of the DVD for now.
‫And let's turn back to Carly.
‫So now is it time to start beef by clicking its icon?
‫We have to run the script code shown in the hook line inside the victim's browser, so I'll copy the
‫code now.
‫The beef interface runs in just a few seconds.
‫Log in using beef.
‫Beef credential.
‫And go back to the DVD tab now, I'll prepare a new message that will contain the hook script of the
‫B framework.
‫Right click and paste the code.
‫Here, we should write the IP address of the Beef Control Center, which is our calling machine.
‫Let's open a new terminal and run the ifconfig command to learn the IP address of Carly.
‫We exceed the maximum character length, right click on the message box and select Inspect Element,
‫make the value of the maxlength more than 70.
‫I think that'll be enough for this demo.
‫So now I complete the IP address.
‫And sign the guest book here, we have the second message and the script code, which was in the body
‫of the message, is executed in the browsers of each of the visitors in the beef control panel.
‫We have a victim browser that is Kali itself because as soon as a guest book is signed, the script
‫is executed in the browser.
‫Now I go to my host machine and visit the excess stored page.
‫Now the second message that means the hook script is executed in my host machines browser.
‫Go to Carly.
‫And in the beef control panel, my host machine is hooked.
‫There are a few tabs in the beef control panel.
‫The main tab displays information about the hooked browser after you've run some command modules.
‫Now, the Commands tab is where the modules can be executed against the hooked browser.
‫This is where most of the beef functionality resides.
‫Each command module has a traffic light icon.
‫A green light indicates that the command module works against the target and should be invisible to
‫the user.
‫The command modules with a grey light means that they are not yet verified against this target.
‫Yellow orange light indicates that the command module works against a target, but may be visible to
‫the user, and the red light means that the command module does not work against this particular target.
‫All right, let's run one of the command modules in the social engineering folder.
‫Select the Petty Theft Command module.
‫The module asks the user for their username and password using a floating div.
‫You can use this module for Facebook, LinkedIn, Windows, etc..
‫So I'll choose Facebook for this example, while my host machine is selected on the left panel, I click
‫the Execute button at the bottom right hand corner of the page.
‫And look, we have a result in the module result history pain.
‫So when we go to the browser and my host machine, we'll see the Facebook dialog box.
‫Looks familiar.
‫It says my session has timed out and I should re-enter my username and password.
‫OK, let's log in.
‫Go back to Cali and in the beef control panel, we have the username and the password values pretty
‫slick, huh?