Lucene search

K
vulnerlabVulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected]) [www.vulnerability-lab.com]VULNERLAB:1275
HistoryNov 05, 2014 - 12:00 a.m.

PayPal Inc - Filter Bypass & Profile Code Execution

2014-11-0500:00:00
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected]) [www.vulnerability-lab.com]
www.vulnerability-lab.com
12
Document Title:
===============
PayPal Inc - Filter Bypass & Profile Code Execution


References:
===========
http://www.vulnerability-lab.com/get_content.php?id=1275

Video: https://www.youtube.com/watch?v=LUksqtG2WrE



Release Date:
=============
2014-11-05


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


Common Vulnerability Scoring System:
====================================
9.1


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


Exploitation Technique:
=======================
Offensiv


Severity Level:
===============
Critical


Technical Details & Description:
================================
The video show the ending results of a successful code execution to the user profile values of the main paypal web-application webscr api request.
In the video Benjamin shows how does the effect looks like when somebody is able to inject code in the most important profile values.
To exploit the issue he used the help center accesspoint in combination to the developer api system.
The severity of the remote code execution is estimated as critical and has been reported to paypal inc in 2013Q3 by the vulnerability-lab team.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected]) [www.vulnerability-lab.com]


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:    [email protected] 	- [email protected] 	       		- [email protected]
Section:    magazine.vulnerability-db.com	- vulnerability-lab.com/contact.php		       	- evolution-sec.com/contact
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 
([email protected] or [email protected]) to get a permission.

				Copyright © 2014 | Vulnerability Laboratory - Evolution Security GmbH ™