[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Prezi Bug Bounty #5 - Client Side Cross Site Scripting & Open Redirect Vulnerability

Document Title:
Prezi Bug Bounty #5 - Client Side Cross Site Scripting & Open Redirect Vulnerability

References (Source):

Release Date:

Vulnerability Laboratory ID (VL-ID):

Common Vulnerability Scoring System:

Product & Service Introduction:
Prezi is a cloud-based presentation software based on a software as a service model. The product employs a zooming user interface (ZUI), which allows 
users to zoom in and out of their presentation media, and allows users to display and navigate through information within a 2.5D or parallax 3D space 
on the Z-axis. Prezi was officially established in 2009 by co-founders Adam Somlai-Fischer, Peter Halacsy and Peter Arvai.

(Copy of the Wikipedia entry: https://en.wikipedia.org/wiki/Prezi)

Abstract Advisory Information:
An independent vulnerability laboratory researcher discovered a client-side redirect web vulnerability in the official Prezi web-application.

Vulnerability Disclosure Timeline:
2016-00-29: Researcher Notification & Coordination (Milan Solanki)
2016-00-30: Vendor Notification (Prezi Security Team)
2016-00-04: Vendor Response/Feedback (Prezi Security Team)
2016-00-16: Vendor Fix/Patch #1 (Prezi Developer Team)
2016-00-22: Security Acknowledgements (Prezi Security Team)
2016-00-17: Security Bulletin  (Prezi Security Team)
2016-00-18: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Affected Product(s):
Product: Online Service - Web Application 2016 Q1

Exploitation Technique:

Severity Level:

Technical Details & Description:
An open redirect web vulnerability has been discovered in the official Prezi web-application.
The bug allows remote attackers to execute external urls by the internal web-application requests via client-side.

The vulnerability is located in the GET parameter of the vulnerable `track` module. The vulnerability allows an remote 
attacker to prepare client-side malicious urls to external sources. The request method to execute is GET and the vulnerability is 
located on the application-side of the online-service. The vulnerability is a classic open redirect web vulnerability.

The security risk of the open redirect web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.0. 
Exploitation of the persistent input validation web vulnerability requires no privileged user account and low or medium user interaction. 
Successful exploitation of the vulnerability results in client-side redirects to malicious sources or client-side phishing.

Request Method(s):
				[+] GET

Vulnerable Module(s):
				[+] /track

Vulnerable Parameter(s):
				[+] URI

Proof of Concept (PoC):
The vulnerability can be exploited by remote attackers without privileged web-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.

Open redirect in the following module:	/track?type=click&enid=[UNIQUE-ID]&&&2003&&&http://EVILURLHERE.com


Solution - Fix & Patch:
Disallow to request not whitelisted webpages and include a tag filter to the enid to prevent as well.
Restrict and filter the parameter and disallow usage of special chars. Encode the GET request to prevent client-ide script code inject.

Security Risk:
The security risk of the client-side open redirect web vulnerability in the Prezi web-application is estimated as low. (CVSS 3.0)

Credits & Authors:
Milan A Solanki - (milans812@xxxxxxxxx) [http://www.safehacking4mas.blogspot.in] [https://www.facebook.com/Mas.Hackers]

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@xxxxxxxxxxxxxxxxxxxxx 	- research@xxxxxxxxxxxxxxxxxxxxx 	       		- admin@xxxxxxxxxxxxxxxxx
Section:    dev.vulnerability-db.com	 	- 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
Programs:   vulnerability-lab.com/submit.php  	- vulnerability-lab.com/list-of-bug-bounty-programs.php	- vulnerability-lab.com/register/

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@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.

				Copyright © 2016 | Vulnerability Laboratory [Evolution Security]

SERVICE: www.vulnerability-lab.com
CONTACT: research@xxxxxxxxxxxxxxxxxxxxx