Document Title:
===============
WhiteHouse Gov Service - Persistent Web Vulnerability


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


Release Date:
=============
2011-11-03


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


Product & Service Introduction:
===============================
http://www.whitehouse.gov/


Abstract Advisory Information:
==============================
The vulnerability-lab researcher (F0x23 & Rem0ve) discovered a persistent script code injection vulnerability on the WhiteHouse Gov website.


Vulnerability Disclosure Timeline:
==================================
2011-11-01:     Vendor Notification
2011-11-03:     Vendor Response/Feedback
2011-11-04:     Vendor Fix/Patch
2011-11-04:     Public or Non-Public Disclosure


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


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


Severity Level:
===============
High


Technical Details & Description:
================================
A persistent script code injection vulnerability is detected on the WhiteHouse Gov website. The vulnerability allows remote 
attackers to implement/inject own malicious script code (persistent) on a web service main module of the website. The successful 
exploitation of the vulnerability results in hijacking of user-,admin- or -backend sessions, manipulation of profile content, 
redirect to external malicious targets(websites), defacement & can lead to malware infiltration via petition.


Vulnerable Module(s):
				                        [+] Profil - Location & Name Input + Output

Affected Module(s):
							[+] Petition - Add, Share & Sign

Picture(s):
			                              	../1.png


Proof of Concept (PoC):
=======================
The vulnerabilities can be exploited by remote attackers. For demonstration or reproduce ...

PoC:
<div class="entry entry-creator ">  
    <div class="title">creator</div>    
    <div class="name">Bernd N</div><!--/name-->
    <div class="details">
      "'><INJECT/EXECUTE PERSISTENT SCRIPT CODE HERE!!><br>
      October 31, 2011<br>
      Signature # 1    </div>
          </div>
      </div>

Reference: https://wwws.whitehouse.gov/petitions/!/petition/hey/VLsNrtR1


INPUT FORM:
<span>City: </span></label>
 <input maxlength="255" name="profile_city" id="edit-profile-city" size="60" value="VA" class="form-text" type="text">
</div>
<input name="form_id" id="edit-user-profile-form" value="user_profile_form" type="hidden">
<div class="form-item clearfix" id="edit-profile-state-wrapper">
 <label for="edit-profile-state"><span>State: </span>

Reference: https://wwws.whitehouse.gov/user/5034619/edit/Personal%20Information


PoC:
                                            ../PoC.txt
                                            ../PoC-Full.txt
                                            ../PoC-Input.txt
                                            ../Reference.txt


Solution - Fix & Patch:
=======================
1. Parse the input fields and restrict characters like () > < \" / to prevent against script tag include.
2. Parse also the vulnerable not filtered output section of name & city were the script code will be executed at the end.
3. Possibility: Implement a specific exception-handling or filter mechanism to prevent against future script code injections.


Security Risk:
==============
The security risk of the persistent script code inject is estimated as high(+).


Credits & Authors:
==================
Vulnerability Research Laboratory -  Alexander Fuchs (F0x23) &  Benjamin Kunz Mejri (Rem0ve)


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:    admin@vulnerability-lab.com 	- support@vulnerability-lab.com 	       - research@vulnerability-lab.com
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 (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory