Document Title:
===============
Blogger CMS AR LoxBlog - CS Cross Site Web Vulnerability


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


Release Date:
=============
2014-03-10


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


Common Vulnerability Scoring System:
====================================
2.9


Abstract Advisory Information:
==============================
An independent laboratory researcher discovered a client-side cross site scripting web vulnerability in the official Blogger Content Management System of the arabish LoxBlog.


Vulnerability Disclosure Timeline:
==================================
2014-03-10:	Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================

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


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


Technical Details & Description:
================================
A client-side cross site scripting web vulnerability has been discovered in the official Blogger Content Management System of the arabish LoxBlog.
The cross site scripting web vulnerability allows an attacker to manipulate client-side browser requests through a vulnerable application module/function.

The cross site scripting vulnerability is located in the `commenting` module when processing to request via GET method manipulated `blogid` values. 
The injected script code execution occurs on the client-side of the web-application in the comments context. The attack vector is non-persistent 
(client-side) and the request method is GET. The security risk of the client-side web vulnerability is estimated as medium(-) with a cvss (common 
vulnerability scoring system) count of 2.8(+)|(-)2.9.

Exploitation of the client-side cross site web vulnerability requires no privileged web-application user account but low or medium user interaction. 
Successful exploitation of the vulnerability results in session hijacking, client-side phishing, client-side external redirects, malicious GET method 
requests and client-side manipulation of the vulnerable or connected module context.

Request Method(s):
				[+] [GET]

Vulnerable Module(s):
				[+] ./commenting

Vulnerable Parameter(s):
				[+] blogid


Proof of Concept (PoC):
=======================
The client-side cross site scripting web vulnerability can be exploited by remote attackers without privileged application user account and with low or medium user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.

Dork:  inurl:/commenting/?blogid=  *.php

Payload:  <<script>alert(/CROSS-SITE-SCRIPTING/)</script>>

PoC: http://localhost:8080/commenting/?blogid=<script>alert(/CROSS-SITE-SCRIPTING/)</script>



Solution - Fix & Patch:
=======================
The security vulnerability can be patched by a secure parse and encode with restriction of the vulnerable `blogid` parameter.


Security Risk:
==============
The security risk of the client-side cross site scripting web vulnerability is estimated as medium(-).


Credits & Authors:
==================
Black V!per

# Tnx To: Root.SmasheR|Black V!per|Mr.Moein|UmPire|Sultan Brain|Alireza_Promis
# M4hdi|Social Engineer|TaK.FaNaR|Linux Lover|hack3core|Saeed.Jok3r - http://iransec.net


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.evolution-sec.com
Contact:    admin@vulnerability-lab.com 	- research@vulnerability-lab.com 	       - admin@evolution-sec.com
Section:    www.vulnerability-lab.com/dev 	- forum.vulnerability-db.com 		       - magazine.vulnerability-db.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, source code, 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 research@vulnerability-lab.com) to get a permission.

				Copyright © 2014 | Vulnerability Laboratory [Evolution Security]