Better WP Security v3.4.3 Wordpress - Web Vulnerabilities

Document Title:
===============
Better WP Security v3.4.3 Wordpress - Web Vulnerabilities


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=691


Release Date:
=============
2012-08-20


Vulnerability Laboratory ID (VL-ID):
====================================
691


Common Vulnerability Scoring System:
====================================
3.5


Product & Service Introduction:
===============================
plugin thereby ensuring that as many security holes as possible are patched without having to worry about 
conflicting features or the possibility of missing anything on your site. With one-click activation for most 
features as well as advanced features for experienced users Better WP Security can help protect any site.

(Copy of the Vendor Homepage: http://wordpress.org/extend/plugins/better-wp-security/  )


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered multiple persistent web vulnerabilities in the Better WP security v3.4.3 Wordpress Application Addon.


Vulnerability Disclosure Timeline:
==================================
2012-08-21:	Public Disclosure


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Remote


Severity Level:
===============
Low


Technical Details & Description:
================================
Multiple persistent input validation vulnerabilities are detected in the Better WP security v3.4.3 Wordpress Application Addon.
The vulnerability allows remote attackers to hijack website customer, moderator or admin sessions with medium or high required user inter 
action. The bugs are located on server side in the Limit Login Attempts, Exception Handling Error & Intrusion Detection module with the 
bound vulnerable email address & error parameter. Successful exploitation can result in wordpress application account steal, client side 
phishing & client-side content request manipulation. Exploitation requires medium or high user inter action & without privileged 
web application user account.

Vulnerable Module(s):
				[+] Better WP Security - Limit Login Attempts & Intrusion Detection
				[+] Exception Handling Error

Vulnerable Parameter(s):
				[+] Email Address
				[+] Error


Proof of Concept (PoC):
=======================
The persistent vulnerability can be exploited by remote attackers with low required user inter action & low privileged 
application user account. For demonstration or reproduce ...

Inject the following example string to the application input (persistent) or parameter (client side)
String:  >"<iframe src=http://www.vulnerability-lab.com></iframe>


Review: Listings

<tr valign="top">
<th scope="row" class="settinglabel">
<label for="" "ll_emailaddress"="">Email Address</label>
</th>
<td class="settingfield">
<input id="ll_emailaddress" name="ll_emailaddress" value="\" type="text">
<[PERSISTENT INJECTED SCRIPT CODE!]")' <="" [email protected]"="">


Review: Exception Handling

<div class="error" style="text-align: center;"><p style="color: red; font-size: 14px; font-weight: 
bold;">Attention !</p><p>
Please add this site now to your <a target="_blank" href="http://managewp.com/wp-admin">ManageWP.com</a> account.  
Or deactivate the Worker plugin to avoid <a target="_blank" href="http://managewp.com/user-guide/security">security issues</a>.	  	
</p></div><div id="message" class="error"><p>Login time period needs to be aan integer greater than 0.</p></div>
<div id="message" class="error"><p>\"><[PERSISTENT INJECTED SCRIPT CODE!]")' <="" is="" 
not="" a="" valid="" ip.<="" p=""></div>


Solution - Fix & Patch:
=======================
The vulnerabilities can be patched by parsing the email address & error exception handling parameters and output listing.


Security Risk:
==============
The security risk of the persistent input validation vulnerabilities are estimated as medium.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team]  -    Benjamin Kunz Mejri ([email protected])


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    [email protected] 	- [email protected] 	       - [email protected]
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory