Document Title:
===============
Prosieben Community 2011 - Persistent Web Vulnerability


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


Release Date:
=============
2011-10-30


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


Common Vulnerability Scoring System:
====================================
5.8


Abstract Advisory Information:
==============================
The Vulnerability Lab Research Team discovered a persistent script code injection vulnerability in the prosieben community website application.


Vulnerability Disclosure Timeline:
==================================
2011-10-23:	Vendor Notification
2011-10-24:	Vendor Response/Feedback
2011-10-27:	Vendor Fix/Patch
2011-11-01:	Public or Non-Public Disclosure


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


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


Severity Level:
===============
Medium


Technical Details & Description:
================================
A persistent script code injection vulnerability is detected on Prosiebens Community vendor website.
Remote attackers can inject/execute malicious script codes on application-side to compromise the community profile of users.
Successful exploitation can result in session hijacking & profile manipulation via script code injection.

Vulnerable Module(s):
					[+] Profile Content & Output - Prosieben Community


Proof of Concept (PoC):
=======================
The vulnerability can be exploited by remote attacker with user account for the community portal.
For demonstration or reproduce ...

<li id="ka_profComment_3464320" class="ka_profComment clearfix" style="height: 0pt;"><div class="ka_profileCommentDate">
vor 3 Wochen <span class="ka_pipe">|</span> <a onclick='var x=".tl(";s_objectID="http://meinecommunity.prosieben.de/service
/displayKickPlace.kickAction?u=34728024&as=122896_1";return this.s_oc?this.s_oc(e):
true' href="/service/displayKickPlace.kickAction?u=34728024&as=122896">Trololol</a> </div><div class="ka_profileCommentImg">
<a onclick='var x=".tl(";s_objectID="http://meinecommunity.prosieben.de/service/displayKickPlace.kickAction?u=34728024
&as=122896_2";return this.s_oc?this.s_oc(e):true' href="/service/displayKickPlace.kickAction?u=34728024&as=122896">
<span style="background-image: url("http://media.kickstatic.com/kickapps/images/122896/icons/defaultMember_122896_portrait
48X48.jpg");"></span></a></div><div class="ka_profileCommentContent clearfix"><p>[PERSISTENT SCRIPT CODE EXECUTION HERE!]>
</p></div><div class="ka_profileCommentControls clearfix"><span class="ka_flag ka_flag_comment"><a class="" onclick='var x="
.tl(";s_objectID="http://meinecommunity.prosieben.de/service/displayKickPlace.kickAction?u=34728024&as=122896#_4";return 
this.s_oc?this.s_oc(e):true' href="#">Beitrag melden</a></span></div></li>


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


Credits & Authors:
==================
Vulnerability Research Laboratory - Alexander Fuchs (F0x23)


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