Government Security
Network Security Resources

Jump to content

Photo

Paypal Bugbounty #9 - Persistent Web Vulnerabilities

security bug vulnerability advisory anonymous cgi php
  • Please log in to reply
No replies to this topic

#1 remove

remove

    Private First Class

  • Members
  • 56 posts

Posted 01 October 2012 - 09:40 PM

Title:
======
Paypal BugBounty #9 - Persistent Web Vulnerabilities


Date:
=====
2012-10-02


References:
===========
http://www.vulnerabi...tent.php?id=646


VL-ID:
=====
646


Common Vulnerability Scoring System:
====================================
7.2


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) [https://www.paypal.c...lateTab">lassen Sie es uns umgehend wissen</a>. Es ist wichtig, uns
Bescheid zu geben, damit wir sicherstellen können, dass niemand ohne Ihr Wissen auf Ihr Konto zugreift.<p>Viele Grüße<br/>Ihr Team
von PayPal</p></td><td width="12" style="background:url(/i/scr/scr_emailRightBorder_13wx1h.gif) left repeat-y;border-right:1px solid #ddd;
"><img src="http://images.paypal.../scr/pixel.gif" border="0" alt=""/></td></tr><tr><td colspan="3">
<img height="13" src="http://images.paypal...s_580wx13h.gif" border="0" alt=""/></td></tr>
</table><table border="0" cellpadding="0" cellspacing="0" id="emailFooter" style="padding-top:20px;font:10px Verdana, Arial, Helvetica,
sans-serif;color:#333;" width="580"><tr><td><div class="footerLinks" style="margin: 5px 0; padding: 0;"><a target="_new"
href="https://www.paypal.c...Center</a><span style="color:#ccc;"> | </span><a
target="_new" href="https://www.paypal.c...></div><p>Bitte antworten Sie nicht auf diese
E-Mail. E-Mails an diese Adresse werden von uns nicht gelesen. Um mit einem Mitarbeiter unseres Kundenservice zu sprechen, loggen Sie sich in Ihr
PayPal-Konto ein und klicken Sie unten auf "Kontakt".</p><p>Copyright © 2012 PayPal. Alle Rechte vorbehalten.<br/><br/>PayPal
(Europe) S.à r.l.et Cie, S.C.A.<br/>Société en Commandite par Actions<br/>Sitz: 22-24 Boulevard Royal, L-2449 Luxemburg<br/>RCS
Luxemburg B 118 349</p><img height="1" width="1" src="https://102.112.2O7....em_email_PP006"
border="0" alt=""/><p class="xptFooter ppid">PayPal-E-Mail-ID PP006</p></td></tr></table></div></body>
</html>
</body>
</html>
</iframe></p></td></tr></tbody>


Solution:
=========
Restrict the companyname input value and parse with an exception handling or secure filter mask. Parse the companyname, addressid &
details output of the security mail notification to prevent script code injects/executions.


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


Credits:
========
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com)


Disclaimer:
===========
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, 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 (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.

Copyright © 2012 | Vulnerability Laboratory





 







Also tagged with one or more of these keywords: security, bug, vulnerability, advisory, anonymous, cgi, php