PayPal has decided to move away from normal SSL due to its unsecure validation. SSL gave attackers a way to steal passwords, bank account sessions, and even put malicious code within a FireFox update. These problems occurred because of the way browsers implemented SSL and the infrastructure of the public key. A simple man-in-the-middle attack can be performed that intercepts the communication between client and server by sending a null-termination certificate to the SSL traffic. When the null-termination certificate is created it includes null characters, such as a \ followed by a 0, in the domain that causes the program to stop reading.
For example if the certificate read:
http://www.paypal.com.\O .thoughtcrime.org
It would be interpreted as:
Anything after the \ 0 would not be read.
McMillan, Robert (June 30, 2009) More Holes Found in Web’s SSL Security Protocol [Web] Retrieved from http://www.pcworld.com/businesscenter/article/169313/more_holes_found_in_webs_ssl_security_protocol.html
PayPal decided to use the extended validation (EV) SSL because it was believed to have provided the solution to the security holes in SSL. With the EV SSL your address bar turns green so you know that the page you are currently on is secure.
Retrieved from: https://www.symantec.com/theme.jsp?themeid=how-ssl-works&tabID=2&inid=vrsn_symc_ssl_FAQ
Cross Site Scripting (XSS) is a major problem that a lot of companies have to address in their own code. PayPal had a scripting error that allowed attackers to create pages that looked like authentic PayPal pages in order to gain user credentials. XSS is a serious problem because it can be used on pages that are using EV SSL. A researcher discovered a way to inject a secure PayPal page without users ever knowing he had done so. The address bar remained green giving the illusion the users were still on the same page. The page then prompted the users for their username and password and sent them to an unauthorized server. He was able to do this by injecting JavaScript code into the PayPal website because there were features on the page that were still only protected by regular SSL.
http://www.theregister.co.uk/2008/05/16/paypal_page_succumbs_to_xss/





