Welcome Guest. | Log In| Register | Membership Benefits
Dark Reading's evil-bytes Weblog

Topics:   Evil Bytes
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

BeEF: XSS Vuln To Hack In Less Than 20 Characters

As I'm finishing another successful Web application penetration test, I'm kicking myself for not noticing a new release of one of my all-time favorite Web hacking tools, the Browser Exploitation Framework (BeEF). BeEFis a fantastic tool for getting across to developers and Web admins the seriousness of vulnerabilities like cross-site scripting (XSS).

Sep 25, 2009 | 02:51 PM | 

By John H. Sawyer
Dark Reading
As I'm finishing another successful Web application penetration test, I'm kicking myself for not noticing a new release of one of my all-time favorite Web hacking tools, the Browser Exploitation Framework (BeEF). BeEFis a fantastic tool for getting across to developers and Web admins the seriousness of vulnerabilities like cross-site scripting (XSS).There is a blurred line between a Web application vulnerability assessment and a Web application penetration test. The former focuses on identifying vulnerabilities, while the latter attempts to exploit the vulnerabilities in order to gain access to sensitive information, compromise users of the site, or take control of the Web server. The reason for the blurring is that to determine whether a vulnerability exists in a Web app, you have to exploit it.

A perfect example of this is XSS and BeEF. To find out if a Web application is vulnerable to XSS, a pen tester (or attacker) will usually insert a JavaScript alert statement into a search field. If the returned page results in a pop-up alert box, then the Web app is vulnerable. An alert box is pretty harmless, so using the alert method as an example during a meeting with the client elicits very little alarm.

Now for BeEF: Take the same scenario and, instead of a JavaScript alert statement, insert a script tag that includes the source tag pointing to your Web server where BeEF is installed (it's a PHP application that requires very little initial configuration). As soon as a client browses to the page you've attacked, BLAM! -- they are hooked and now a zombie under your control within the BeEF Web interface.

While this is a very simple example, it illustrates the fine line between determining whether a Web vulnerability exists, and exploiting it to take control of a user's Web browser. SQL injection is another vulnerability where the same blurriness exists. Inputting a single quote in a login field could cause the back-end SQL query to error out, while adding a few hyphens, ones, and equals sign means you could slip right past the authentication.

Meantime, BeEF is a wonderful tool, and the latest version adds some awesome features, including integration with the Metasploit Framework, the ability to exploit extensions in Mozilla, better detection of the victim's browser, and tiered logging (so report writing is a little easier because you know exactly what happened). If you haven't used it before, then take a look -- it's a seriously powerful tool and should be part of any Web app pen tester's toolkit.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
  May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008