|
|
Samsung SecEmailUI script injection | ||||
| Project Member Reported by hawkes@google.com, Jul 29 2015 | Back to list | ||||
The default Samsung email client's email viewer and composer (implemented in SecEmailUI.apk) doesn't sanitize HTML email content for scripts before rendering the data inside a WebView. This allows an attacker to execute arbitrary JavaScript when a user views a HTML email which contains HTML script tags or other events. At the very least the JavaScript could exploit the attack surface provided within the WebView control. It might also be possible to access local file content or emails depending on the full configuration of the WebView, although this hasn't been tested fully. This can also be exploited locally with the com.samsung.android.email.intent.action.QUICK_REPLY_BACKGROUND intent which will include attacker controlled HTML in the sending email. If the final message was viewed it would be possible for the script to extract the original message from the Document object and potentially post that information to another server. Attached is a simple SMTP client in Python to send an HTML message with script contents to the device. The "me", "you", "me_password" and "smtp_server" variables need to be changed to ones appropriate for the sending email account and the receiving account on the phone. When the resulting email is viewed it should display the URL of the page which is of the form email://M/N where M is the email account ID and N is the message ID which proves that the script code executed. This bug is subject to a 90 day disclosure deadline. If 90 days elapse without a broadly available patch, then the bug report will automatically become visible to the public.
Project Member
Comment 1
by
scvitti@google.com,
Jul 30 2015
,
Oct 22 2015
This appears to be unfixed on G925VVRU4B0G9
,
Oct 23 2015
,
Oct 27 2015
Fix is scheduled for November MR according to Samsung.
,
Nov 1 2015
I just tested this on myself. I did get an email but all it said was email//87 Doesn't seem to have done anything at all.
,
Jan 2 2016
I just tested this on myself. I did get an email but all it said was email//87 Doesn't seem to have done anything at all.
,
Feb 5 2016
Closing, as the patch has now been released. |
|||||
| ► Sign in to add a comment | |||||