Re:Paypal Android App Remote Code Execution
by stusmall on Saturday March 29, 2014 @02:19PM
(#7493237)
>It was recently discovered that applications do not even need to have a Javascript Interface in their code to be vulnerable to this attack. This is because a Javascript Interface is implemented core webview code in Android versions before 4.2. Meaning that every single application that loads a webview over cleartext is vulnerable to this attack.
Maybe its because I haven't properly had coffee yet or because I've never used WebView in android but I'm having trouble parsing this. From the small code snippet they provided it shows them enabling javascript and adding an interface. Is this just a general comment for other apps that are working on HTTP or broken HTTPS or does it relate to this exploit?
Re:Paypal Android App Remote Code Execution
by dmayer on Saturday March 29, 2014 @04:42PM
(#7493849)
There is a CVE (CVE-2012-6636) [1,2] related to the general issue they are mentioning. Basically one could use reflection to call any public function on any class in the app. Since Android 4.2 one now needs to add the @JavascriptInterface decorator to explicitly expose methods. At least this is my current understanding of this.
If the app then uses HTTP or HTTPS without certificate validation, it is easily possible to inject JavaScrpipt code even when no Cross-Site Scripting vulnerability exists in the app.
Re:Paypal Android App Remote Code Execution
by tkorri on Sunday March 30, 2014 @03:44AM
(#7495526)
This also caught my eye... But then again there are many examples where Paypal has handled issues badly, so I'd guess this just the way they want their brand to be perceived.
Re:Paypal Android App Remote Code Execution
by zaidf on Saturday March 29, 2014 @07:14PM
(#7494379)
Someone unknown added a phone number and a new mobile pin to my paypal account recently. I called paypal support and they walked me through changing the pin. Few minutes later, the pin was changed once again by the unknown person. I call paypal again and they walk me through a similar process again. Finally it stopped but it left me feeling very vulnerable especially because I'd enabled two factory auth and it did little to prevent it.
Weird enough no funds from my account disappeared. Not sure if me acting so far(within minutes of compromise) had to do with it.
Re:Paypal Android App Remote Code Execution
by jonny_eh on Saturday March 29, 2014 @07:54PM
(#7494512)
I'm guessing an engineer added the 'proceed' call during development because the dev servers had invalid certs, and they forgot to change it back before committing.
Re:Paypal Android App Remote Code Execution
by tokenizerrr on Saturday March 29, 2014 @03:06PM
(#7493488)
What kind of code can be executed through the Javascript interface? They seem to claim it's not specific to Paypal's implementation and these seem fairly common. I was under the impression they only expose various methods and variables. How can they be exploited?
Re:Paypal Android App Remote Code Execution
by gberger on Saturday March 29, 2014 @05:29PM
(#7494051)
An attacker can show the user a page identical to PayPal's and convincingly ask them for their credentials. The submission would send the credentials to the attacker.
Maybe its because I haven't properly had coffee yet or because I've never used WebView in android but I'm having trouble parsing this. From the small code snippet they provided it shows them enabling javascript and adding an interface. Is this just a general comment for other apps that are working on HTTP or broken HTTPS or does it relate to this exploit?
If the app then uses HTTP or HTTPS without certificate validation, it is easily possible to inject JavaScrpipt code even when no Cross-Site Scripting vulnerability exists in the app.
[1] https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-66...
[2] https://labs.mwrinfosecurity.com/advisories/2013/09/24/webvi...
Wow, good job PayPal.
That does not sound good.
Weird enough no funds from my account disappeared. Not sure if me acting so far(within minutes of compromise) had to do with it.