HackDig : Dig high-quality web security articles for hacker

Paypal Inc Bug Bounty #30 - Filter Bypass & Persistent Vulnerabilities

2014-10-06 12:00
Document Title:
Paypal Inc Bug Bounty #30 - Filter Bypass & Persistent Vulnerabilities

References (Source):

Release Date:

Vulnerability Laboratory ID (VL-ID):

Common Vulnerability Scoring System:

Product & Service Introduction:
PayPal is a global e-commerce business allowing payments and money transfers to be made through the Internet. Online
transfers serve as electronic alternatives to paying with traditional paper methods, such as checks and money orders.
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
spending limit. After that point, PayPal will attempt to take funds for a purchase from funding sources according to a
funding hierarchy. If you set one of the funding sources as Primary, it will default to that, within that level of the
(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
funding source) (It can bypass the Balance); a verified bank account; other funding sources, such as non-PayPal credit
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 multiple web vulnerabilities in the official PayPal Here mobile
notify me online service web-application.

Vulnerability Disclosure Timeline:
2014-09-26: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Affected Product(s):

Exploitation Technique:

Severity Level:

Technical Details & Description:
2 persistent POST Inject Vulnerabilities has been discovered in the official PayPal Here mobile Notify Me online
service web-application.
The vulnerability allows remote attackers to inject own malicious script code on the application-side of the vulnerable
web function.

The first 2 vulnerabilities are located in the `first_name` and `last_name` values of the `Notify Me` online service
Remote attacker are able to inject own malicious script codes in the firstname and lastname values of the Notify Me
send POST method request.
The execution of the injected script code occurs in the `biz.paypal` notify mail that arrives after the successful POST
method request of the
paypal api and web-application. The context execution is located in the mail header next to the introduction to the
paypal customer.

A input filter validation bypass vulnerability has been discovered in the official PayPal Here mobile Notify Me online
service web-application.
To inject the values the attacker needs to use a session tamper to interact.

During the pentests the input fields disallows to insert of script codes (firstname & lastname). We tried to manipulate
the POST request which
is not connected to the input validation form (after a first load) with own malicious test values. The result was the
successful execution of
the malicious test code in the paypal notify me service mail. The protection of the input was not connected to the
session request which results
in a successful bypass by manipulation of the post values after the first web request.

The security risk of the persistent web vulnerability is estimated as medium with a cvss (common vulnerability scoring
system) count of 3.5.
Exploitation of the application-side web vulnerability requires no privileged web-application user account but low or
medium user interaction.
Successful exploitation of the vulnerabilities result in persistent phishing mails, session hijacking, persistent
external redirect to malicious
sources and application-side manipulation of affected or connected module context.

Request Method(s):
[+] POST

Vulnerable Module(s):
[+] PayPal Here - Notify Me

Vulnerable Input Field(s):
[+] Firstname
[+] Lastname

Vulnerable Parameter(s):
[+] first_name
[+] last_name

Affected Module(s):
[+] Notification Mail - You’re in line to get PayPal Here™

Proof of Concept (PoC):
The persistent vulnerability can be exploited by remote attackers without privileged application user account and with
low or medium user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below
to continue.

Manual steps to reproduce the application-side vulnerability ...

1. Open the paypal.com website and surf to the notify me service application site
2. Include your email and the random company name, firstname and lastname as regular (Do not save to notify yet!)
3. Start a session tamper to manipulate the request after the first attempt
4. Change the vulnerable firstname and lastname values with own script code payloads and continue to intercept the
5. Open your mailbox and review the arrived paypal inc notify me service mail of the website formular
6. The persistent execution occurs in the header location next to the paypal customer introduction word `Dear
Note: The attacker is now able to manipulate the complete mail body and header of the notify me context to compromise
other user accounts
7. Successful reproduce of the remote vulnerability!

PoC: Notification Mail - Firstname & Lastname

<td style="font-family:verdana,sans-serif; font-size:13px; color:rgb(54, 54, 54);
text-align:left; "><div class="mktEditable" id="copy"><p><br><span style="font-family: arial,helvetica,sans-serif;
font-size: 12px;">Dear svenja "><[PERSISTENT INJECET SCRIPT CODE! FIRSTNAME & LASTNAME];)" <, <="" span=""></p>
<p><span style="font-family: arial,helvetica,sans-serif; font-size: 12px;">
Thank you for your interest in PayPal Here! You are now a confirmed member of the PayPal Here “
Exclusive Release” wait list.
PayPal Here will be available shortly and you will be notified with instructions on how to get your free mobile
card reader and access to the app through iTunes or the Android Market (Play).</span></p>
<p><span style="font-family: arial,helvetica,sans-serif; font-size: 12px;">PayPal Here will make a big difference to
your business.
Instead of chasing payments or missing out on sales, you’ll be able to plug the card reader into your smart
phone and get paid on the spot. </span></p>

--- PoC Session Logs [POST] ---
POST (Request): Standard
email=bkm () evolution-sec com

POST (Request): Manipulated
email=bkm () evolution-sec com


Solution - Fix & Patch:
The vulnerability can be patched by a secure encode and parse of the firstname and lastname values in the notify me
POST method request.
Restrict the notify me input fields and disallow special chars. Parse the in the outgoing mail context the names that
are stored in the
dbms to prevent further script code executions. Connect a token to the session to prepare exceptions that prevent
malicious interaction.

Security Risk:
The security risk of the two persistent input validation vulnerabilities via POST method request are estimated as
The security risk of the filter bypass vulnerability e in the paypal inc notify me form is estimated as medium.

Credits & Authors:
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm () evolution-sec com) [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 -
Contact: admin () vulnerability-lab com - research () vulnerability-lab com - admin ()
evolution-sec com
Section: dev.vulnerability-db.com - forum.vulnerability-db.com -
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab -
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php -
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.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 research () vulnerability-lab com) to get a permission.

Copyright © 2014 | Vulnerability Laboratory [Evolution Security]

DOMAIN: www.vulnerability-lab.com
CONTACT: research () vulnerability-lab com

Sent through the Full Disclosure mailing list
Web Archives & RSS: http://seclists.org/fulldisclosure/

Source: 32/tcO/4102/erusolcsidlluf/gro.stsilces

Read:2932 | Comments:0 | Tags:No Tag

“Paypal Inc Bug Bounty #30 - Filter Bypass & Persistent Vulnerabilities”0 Comments

Submit A Comment



Blog :

Verification Code:


Share high-quality web security related articles with you:)


Tag Cloud