Document Title: =============== Paypal Bug Bounty #21 - Persistent Encoding Vulnerability References (Source): ==================== Release Date: ============= 2012-11-24 Vulnerability Laboratory ID (VL-ID): ==================================== 684 Common Vulnerability Scoring System: ==================================== 3 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: [] Abstract Advisory Information: ============================== The Vulnerability Laboratory Research Team discovered a Web Vulnerability in the official Paypal Plaza website application. Vulnerability Disclosure Timeline: ================================== 2012-08-14: Researcher Notification & Coordination 2012-08-14: Vendor Notification 2012-08-16: Vendor Response/Feedback 2012-10-29: Vendor Fix/Patch by PayPal Inc 2012-11-25: Public or Non-Public Disclosure Discovery Status: ================= Published Exploitation Technique: ======================= Remote Severity Level: =============== Low Technical Details & Description: ================================ A persistent input validation vulnerability is detected in the official Paypal Plaza website application (Customers). The bug allows an attacker (remote) to implement/inject malicious script code on the application-side (persistent) of the paypal plaza egreetings web service. The vulnerability is located in the (Step 5 Preview) eGreeting module notification with the bound vulnerable your name and recipient’s name parameters. The vulnerability can be exploited by remote attackers with low or medium required user inter action and without privileged Customer/Pro/Seller account. Successful exploitation of the vulnerability can lead to session hijacking (customers), account steal via persistent web attacks, persistent phishing or stable (persistent) mail notification context manipulation. Vulnerable Type(s): [+] eGreetings Service Vulnerable Site(s): [+] Paypal Plaza ( Vulnerable Module(s): [+] Step 5 Preview for eGreeting Vulnerable Parameter(s): [+] Your Name [+] Recipient’s Name Affected Section(s): [+] Notification Mail - Dear > [value] Proof of Concept (PoC): ======================= The persistent input validation vulnerability can be exploited by remote attackers with low or medium required user inter action. For demonstration or reproduce ... Review: Notification Mail - eGreetings Card Notification You have received a eCard from your loved one.
Betreff: You have received a eCard from your loved one.
Von: =?utf-8?B?Ij48aWZyYW1lIHNyYz1hIG9ubG9hZD1hbGVydCgiSEkiKSA8?=
Datum: 14.08.2012 05:15



View your eCard now. Solution - Fix & Patch: ======================= 2012-10-29: Vendor Fix/Patch by PayPal Inc Security Risk: ============== The security risk of the persistent input validation vulnerability in the mail notification service filter is estimated as medium. Credits & Authors: ================== Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ( 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: - - Contact: - - Section: - - Social:!/vuln_lab - - Feeds: - - 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 ( or to get a permission. Copyright © 2012 | Vulnerability Laboratory