Search...

Paypal BugBounty #13 - Mail Encoding Web Vulnerability

2013-06-17T00:00:00

ID VULNERLAB:650
Type vulnerlab
Reporter Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (storm@vulnerability-lab.com)
Modified 2013-06-17T00:00:00

Description

                                        
                                            Document Title:
===============
Paypal BugBounty #13 - Mail Encoding Web Vulnerability


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

PayPal Security UID: cga1a7oh




Release Date:
=============
2013-06-17


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


Common Vulnerability Scoring System:
====================================
3.5


Product & Service Introduction:
===============================
PayPal is a global e-commerce business allowing payments and money transfers to be made through the Internet. Online money 
transfers serve as electronic alternatives to paying with traditional paper methods, such as checks and money orders. Originally, 
a PayPal account could be funded with an electronic debit from a bank account or by a credit card at the payer s choice. But some 
time in 2010 or early 2011, PayPal began to require a verified bank account after the account holder exceeded a predetermined 
spending limit. After that point, PayPal will attempt to take funds for a purchase from funding sources according to a specified 
funding hierarchy. If you set one of the funding sources as Primary, it will default to that, within that level of the hierarchy 
(for example, if your credit card ending in 4567 is set as the Primary over 1234, it will still attempt to pay money out of your 
PayPal balance, before it attempts to charge your credit card). The funding hierarchy is a balance in the PayPal account; a 
PayPal credit account, PayPal Extras, PayPal SmartConnect, PayPal Extras Master Card or Bill Me Later (if selected as primary 
funding source) (It can bypass the Balance); a verified bank account; other funding sources, such as non-PayPal credit cards.
The recipient of a PayPal transfer can either request a check from PayPal, establish their own PayPal deposit account or request 
a transfer to their bank account.

PayPal is an acquirer, performing payment processing for online vendors, auction sites, and other commercial users, for which it 
charges a fee. It may also charge a fee for receiving money, proportional to the amount received. The fees depend on the currency 
used, the payment option used, the country of the sender, the country of the recipient, the amount sent and the recipient s account 
type. In addition, eBay purchases made by credit card through PayPal may incur extra fees if the buyer and seller use different currencies.

On October 3, 2002, PayPal became a wholly owned subsidiary of eBay. Its corporate headquarters are in San Jose, California, United 
States at eBay s North First Street satellite office campus. The company also has significant operations in Omaha, Nebraska, Scottsdale, 
Arizona, and Austin, Texas, in the United States, Chennai, Dublin, Kleinmachnow (near Berlin) and Tel Aviv. As of July 2007, across 
Europe, PayPal also operates as a Luxembourg-based bank.

On March 17, 2010, PayPal entered into an agreement with China UnionPay (CUP), China s bankcard association, to allow Chinese consumers 
to use PayPal to shop online.PayPal is planning to expand its workforce in Asia to 2,000 by the end of the year 2010.
Between December 4ñ9, 2010, PayPal services were attacked in a series of denial-of-service attacks organized by Anonymous in retaliation 
for PayPal s decision to freeze the account of WikiLeaks citing terms of use violations over the publication of leaked US diplomatic cables.

(Copy of the Homepage: www.paypal.com) [http://en.wikipedia.org/wiki/PayPal]


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered a Web Vulnerability in the official Paypal ecommerce website application.


Vulnerability Disclosure Timeline:
==================================
2012-07-07:	Researcher Notification & Coordination (Ibrahim Mosaad El-Sayed)
2012-07-07:	Vendor Notification (PayPal Site Security Team - Bug Bounty Program)
2012-08-13:	Vendor Response/Feedback (PayPal Site Security Team - Bug Bounty Program)
2012-06-14:	Vendor Fix/Patch (PayPal Site Developer Team - PayPal Inc)
2012-06-18:	Public Disclosure (Vulnerability Laboratory)


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


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


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


Technical Details & Description:
================================
A persistent input validation vulnerability is detected in the official Paypal ecommerce website content management system (Customer/Pro/Seller).
The bug allows remote attackers to implement/inject malicious script code on the application-side (persistent) of the paypal web service.

The vulnerability is located in the request money module with the bound vulnerable subject parameter. The bug affects the important request money 
mail notifications when processing to send to a receiver. The vulnerability can be exploited by remote attackers with low required user inter 
action and privileged Customer/Pro/Seller account. Successful exploitation of the vulnerability can lead to session hijacking (customers), account 
steal via persistent web attack (mail), persistent phishing or stable (persistent) context manipulation of notification mails.


Vulnerable Type(s):
                          [+] Customer/Pro/Seller Accounts

Vulnerable Section(s):
                          [+] Request Money

Vulnerable Module(s):
                          [+] Money Request Mail Notification

Vulnerable Parameter(s):
                          [+] Subject


Proof of Concept (PoC):
=======================
The vulnerability can be exploited by remote attackers with Customer/Pro/Seller Account & low required user inter action.
For demonstration or reproduce ...


Review: Money Request Mail Notification

&lt;tbody&gt;&lt;tr&gt;
&lt;td&gt;From: &lt;/td&gt;&lt;td&gt;service@paypal.com&lt;/td&gt;
	&lt;/tr&gt;	
	&lt;tr&gt;	
&lt;td&gt;To: &lt;/td&gt;&lt;td&gt;the_st_1341111965_per@mail.com&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;	
&lt;td&gt;Date: &lt;/td&gt;&lt;td&gt;Jul 6, 2012 15:41:55 PDT&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
&lt;td&gt;Subject:  &lt;/td&gt;&lt;td&gt;"&gt;"&lt;[PERSISTENT INJECTED SCRIPT CODE!]&gt;"&gt;"&gt;"&lt;i&lt; td=""&gt;
&lt;/i&lt;&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;

URL: https://www.paypal.com/cy/cgi-bin/invoiceweb?cmd=_request-money


Solution - Fix & Patch:
=======================
2012-06-14:	Vendor Fix/Patch by PayPal Inc


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


Credits & Authors:
==================
Vulnerability Laboratory [Research Team]  -    Ibrahim El-Sayed (storm@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.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, 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 support@vulnerability-lab.com) to get a permission.

    				   	Copyright © 2013 | Vulnerability Laboratory

JSON Vulners Source

Initial Source

{"sourceData": "Document Title:\r\n===============\r\nPaypal BugBounty #13 - Mail Encoding Web Vulnerability\r\n\r\n\r\nReferences (Source):\r\n====================\r\nhttp://www.vulnerability-lab.com/get_content.php?id=650\r\n\r\nPayPal Security UID: cga1a7oh\r\n\r\n\r\n\r\n\r\nRelease Date:\r\n=============\r\n2013-06-17\r\n\r\n\r\nVulnerability Laboratory ID (VL-ID):\r\n====================================\r\n650\r\n\r\n\r\nCommon Vulnerability Scoring System:\r\n====================================\r\n3.5\r\n\r\n\r\nProduct & Service Introduction:\r\n===============================\r\nPayPal is a global e-commerce business allowing payments and money transfers to be made through the Internet. Online money \r\ntransfers serve as electronic alternatives to paying with traditional paper methods, such as checks and money orders. Originally, \r\na PayPal account could be funded with an electronic debit from a bank account or by a credit card at the payer s choice. But some \r\ntime in 2010 or early 2011, PayPal began to require a verified bank account after the account holder exceeded a predetermined \r\nspending limit. After that point, PayPal will attempt to take funds for a purchase from funding sources according to a specified \r\nfunding hierarchy. If you set one of the funding sources as Primary, it will default to that, within that level of the hierarchy \r\n(for example, if your credit card ending in 4567 is set as the Primary over 1234, it will still attempt to pay money out of your \r\nPayPal balance, before it attempts to charge your credit card). The funding hierarchy is a balance in the PayPal account; a \r\nPayPal credit account, PayPal Extras, PayPal SmartConnect, PayPal Extras Master Card or Bill Me Later (if selected as primary \r\nfunding source) (It can bypass the Balance); a verified bank account; other funding sources, such as non-PayPal credit cards.\r\nThe recipient of a PayPal transfer can either request a check from PayPal, establish their own PayPal deposit account or request \r\na transfer to their bank account.\r\n\r\nPayPal is an acquirer, performing payment processing for online vendors, auction sites, and other commercial users, for which it \r\ncharges a fee. It may also charge a fee for receiving money, proportional to the amount received. The fees depend on the currency \r\nused, the payment option used, the country of the sender, the country of the recipient, the amount sent and the recipient s account \r\ntype. In addition, eBay purchases made by credit card through PayPal may incur extra fees if the buyer and seller use different currencies.\r\n\r\nOn October 3, 2002, PayPal became a wholly owned subsidiary of eBay. Its corporate headquarters are in San Jose, California, United \r\nStates at eBay s North First Street satellite office campus. The company also has significant operations in Omaha, Nebraska, Scottsdale, \r\nArizona, and Austin, Texas, in the United States, Chennai, Dublin, Kleinmachnow (near Berlin) and Tel Aviv. As of July 2007, across \r\nEurope, PayPal also operates as a Luxembourg-based bank.\r\n\r\nOn March 17, 2010, PayPal entered into an agreement with China UnionPay (CUP), China s bankcard association, to allow Chinese consumers \r\nto use PayPal to shop online.PayPal is planning to expand its workforce in Asia to 2,000 by the end of the year 2010.\r\nBetween December 4\u00f19, 2010, PayPal services were attacked in a series of denial-of-service attacks organized by Anonymous in retaliation \r\nfor PayPal s decision to freeze the account of WikiLeaks citing terms of use violations over the publication of leaked US diplomatic cables.\r\n\r\n(Copy of the Homepage: www.paypal.com) [http://en.wikipedia.org/wiki/PayPal]\r\n\r\n\r\nAbstract Advisory Information:\r\n==============================\r\nThe Vulnerability Laboratory Research Team discovered a Web Vulnerability in the official Paypal ecommerce website application.\r\n\r\n\r\nVulnerability Disclosure Timeline:\r\n==================================\r\n2012-07-07:\tResearcher Notification & Coordination (Ibrahim Mosaad El-Sayed)\r\n2012-07-07:\tVendor Notification (PayPal Site Security Team - Bug Bounty Program)\r\n2012-08-13:\tVendor Response/Feedback (PayPal Site Security Team - Bug Bounty Program)\r\n2012-06-14:\tVendor Fix/Patch (PayPal Site Developer Team - PayPal Inc)\r\n2012-06-18:\tPublic Disclosure (Vulnerability Laboratory)\r\n\r\n\r\nDiscovery Status:\r\n=================\r\nPublished\r\n\r\n\r\nExploitation Technique:\r\n=======================\r\nRemote\r\n\r\n\r\nSeverity Level:\r\n===============\r\nLow\r\n\r\n\r\nTechnical Details & Description:\r\n================================\r\nA persistent input validation vulnerability is detected in the official Paypal ecommerce website content management system (Customer/Pro/Seller).\r\nThe bug allows remote attackers to implement/inject malicious script code on the application-side (persistent) of the paypal web service.\r\n\r\nThe vulnerability is located in the request money module with the bound vulnerable subject parameter. The bug affects the important request money \r\nmail notifications when processing to send to a receiver. The vulnerability can be exploited by remote attackers with low required user inter \r\naction and privileged Customer/Pro/Seller account. Successful exploitation of the vulnerability can lead to session hijacking (customers), account \r\nsteal via persistent web attack (mail), persistent phishing or stable (persistent) context manipulation of notification mails.\r\n\r\n\r\nVulnerable Type(s):\r\n [+] Customer/Pro/Seller Accounts\r\n\r\nVulnerable Section(s):\r\n [+] Request Money\r\n\r\nVulnerable Module(s):\r\n [+] Money Request Mail Notification\r\n\r\nVulnerable Parameter(s):\r\n [+] Subject\r\n\r\n\r\nProof of Concept (PoC):\r\n=======================\r\nThe vulnerability can be exploited by remote attackers with Customer/Pro/Seller Account & low required user inter action.\r\nFor demonstration or reproduce ...\r\n\r\n\r\nReview: Money Request Mail Notification\r\n\r\n<tbody><tr>\r\n<td>From: </td><td>service@paypal.com</td>\r\n\t</tr>\t\r\n\t<tr>\t\r\n<td>To: </td><td>the_st_1341111965_per@mail.com</td>\r\n\t</tr>\r\n\t<tr>\t\r\n<td>Date: </td><td>Jul 6, 2012 15:41:55 PDT</td>\r\n\t</tr>\r\n\t<tr>\r\n<td>Subject:\u00a0\u00a0</td><td>\">\"<[PERSISTENT INJECTED SCRIPT CODE!]>\">\">\"<i< td=\"\">\r\n</i<></td></tr>\r\n</tbody>\r\n\r\nURL: https://www.paypal.com/cy/cgi-bin/invoiceweb?cmd=_request-money\r\n\r\n\r\nSolution - Fix & Patch:\r\n=======================\r\n2012-06-14:\tVendor Fix/Patch by PayPal Inc\r\n\r\n\r\nSecurity Risk:\r\n==============\r\nThe security risk of the persistent script code inject vulnerability is estimated as medium(+).\r\n\r\n\r\nCredits & Authors:\r\n==================\r\nVulnerability Laboratory [Research Team] - Ibrahim El-Sayed (storm@vulnerability-lab.com)\r\n\r\n\r\nDisclaimer & Information:\r\n=========================\r\nThe information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, \r\neither expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-\r\nLab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business \r\nprofits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some \r\nstates do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation \r\nmay not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases \r\nor trade with fraud/stolen material.\r\n\r\nDomains: www.vulnerability-lab.com \t- www.vuln-lab.com\t\t\t - www.vulnerability-lab.com/register\r\nContact: admin@vulnerability-lab.com \t- support@vulnerability-lab.com \t - research@vulnerability-lab.com\r\nSection: video.vulnerability-lab.com \t- forum.vulnerability-lab.com \t\t - news.vulnerability-lab.com\r\nSocial:\t twitter.com/#!/vuln_lab \t\t- facebook.com/VulnerabilityLab \t - youtube.com/user/vulnerability0lab\r\nFeeds:\t vulnerability-lab.com/rss/rss.php\t- vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php\r\n\r\nAny modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. \r\nPermission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other \r\nmedia, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and \r\nother information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), \r\nmodify, use or edit our material contact (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.\r\n\r\n \t\t\t\t \tCopyright \u00a9 2013 | Vulnerability Laboratory\r\n\r\n\r\n\r\n", "description": "", "reporter": "Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (storm@vulnerability-lab.com)", "href": "http://www.vulnerability-lab.com/get_content.php?id=650", "type": "vulnerlab", "viewCount": 6, "references": [], "lastseen": "2019-07-10T14:58:34", "published": "2013-06-17T00:00:00", "cvelist": [], "id": "VULNERLAB:650", "modified": "2013-06-17T00:00:00", "title": "Paypal BugBounty #13 - Mail Encoding Web Vulnerability", "edition": 2, "cvss": {"score": 0.0, "vector": "NONE"}, "bulletinFamily": "exploit", "enchantments": {"dependencies": {"references": [], "modified": "2019-07-10T14:58:34", "rev": 2}, "score": {"value": -0.1, "vector": "NONE", "modified": "2019-07-10T14:58:34", "rev": 2}, "vulnersScore": -0.1}, "scheme": null, "immutableFields": []}