Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Vulnerability Lab (researchvulnerability-lab.com)
Date: Sat Jun 08 2013 - 20:37:03 CDT
Paypal Bug Bounty #12 - PPM Listing Vulnerability
Common Vulnerability Scoring System:
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
(Copy of the Homepage: www.paypal.com) [http://en.wikipedia.org/wiki/PayPal]
The Vulnerability Laboratory Research Team discovered a Web Vulnerability in the official Paypal ecommerce website application.
2012-07-06: Researcher Notification & Coordination
2012-07-06: Vendor Notification
2012-08-29: Vendor Response/Feedback
2012-05-30: Vendor Fix/Patch
2012-06-01: Public Disclosure
Multiple persistent input validation vulnerabilities are detected in the official Paypal ecommerce website content management system (Customer/Pro/Seller).
The bugs allow remote attackers to implement/inject malicious script code on the application side (persistent) of the paypal web service.
The vulnerability is located in the Paypal Manager > vtOrderTransaction module with the bound vulnerablebillingAddress1, billingAddress2 &
billingAddress1Optional parameter. The bug affects the important Add formular & transactions listing. 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, persistent phishing or stable (persistent) context manipulation.
[+] Customer/Pro/Seller Accounts
[+] Paypal Manager
[+] vtOrderTransaction (Add & Listing)
[+] billingAddress1, billingAddress2 & billingAddress1Optional
[+] Add Formular & Transaction Listing
Proof of Concept:
The vulnerability can be exploited by remote attackers with Customer/Pro/Seller Account & low required user inter action.
For demonstration or reproduce ...
Review: Paypal Manager - vtOrderTransaction (Add & Listing)
<p class="fieldRow" id="billingAddress1Optional" value="" type="text"><[INJECTED PERSISTENT SCRIPT CODE])' <"="">
<label for="billingAddress1" accesskey="12">Billing address
<span>[<a href="#" class="autoTooltip" title="Enter the address where your customer receives credit card bills">?</a>]</span>
<input name="billingAddress1" id="billingAddress1" value="" type="text"><[INJECTED PERSISTENT SCRIPT CODE])' <"="">
Restrict the billingAddress1, billingAddress2 & billingAddress1Optional input fields. Parse them with an exception handling or secure filter mask.
Parse the billingAddress1, billingAddress2 & billingAddress1Optional output listings of the OrderTransaction or Transaction Artikels (modules)
to prevent script code injects/executions.
The security risk of the persistent script code inject vulnerability is estimated as high.
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkmvulnerability-lab.com)
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: adminvulnerability-lab.com - supportvulnerability-lab.com - researchvulnerability-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 (adminvulnerability-lab.com or supportvulnerability-lab.com) to get a permission.
Copyright © 2013 | Vulnerability Laboratory
VULNERABILITY RESEARCH LABORATORY
LABORATORY RESEARCH TEAM
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/