DRD19-J. Properly verify server certificate on SSL/TLS

Android apps that use SSL/TLS protocols for secure communication should properly verify server certificates. The basic verification includes:

• verify that the subject (CN) of X.509 certificate and the URL matches
• verify that the certificate is signed by the trusted CA
• verify that the signature is correct
• verify that the certificate is not expired

Android SDK  4.0 and later offers packages to implement capabilities to establish network connections. For example, by using java.net, javax.net, android.net or  org.apache.http, a developer can create server sockets or HTTP connection. org.webkit offers functions necessary to implement web browsing capabilities.

A developer has the freedom to customize their SSL implementation, and thus has a responsibility to properly use SSL depending on the intent of the app as well as the environment the apps are used in. If the SSL is not correctly used, a user's sensitive data may leak via the vulnerable SSL communication channel.

Fahl et al [Fahl 2012] summarises the following patterns of the insecure use of SSL:

Trusting All Certificates

* implement the TrustManager interface so that it will trust all  the server certificate (regardless of who signed it, what is the CN etc.)

 

Allowing All Hostnames

* does not verify if the certificate is issued for the URL the client is connecting to

    * when a client connects to example.com, it will accept a server certificate issued for some-other-domain.com

 

Mixed-Mode / No SSL

* A developer mixes secure and insecure connections in the same app or does not use SSL at all.

 

On Android, using HttpURLConnection is recommended to implement HTTP client.

On Android, using HttpURLConnection is recommended for HTTP client implementation.

Noncompliant Code Example

The following code creates a file on the external storage and saves sensitive information to the file:

private String filename = "myfile"

private String string = "sensitive data such as credit card number"
FileOutputStream fos = null;

try {
  file file = new File(getExternalFilesDir(TARGET_TYPE), filename);
  fos = new FileOutputStream(file, false);
  fos.write(string.getBytes());
} catch (FileNotFoundException e) {
  // handle FileNotFoundException
} catch (IOException e) {
  // handle IOException
} finally {
  if (fos != null) {
    try {
  	fos.close();
    } catch (IOException e) {
    }
  }
}

Proof of Concept

Typically, an application stores files in the directory as follows:

/sdcard/Android/data/com.company.app/files/save/appdata/save_appdata

Compliant Solution (Save a File on Internal Storage)

The following code uses the openFileOutput() method to create "myfile" in an application data directory with permission set to MODE_PRIVATE so that other apps cannot access the file:

private String filename = "myfile"
private String string = "sensitive data such as credit card number"
FileOutputStream fos = null;

try {
   fos = openFileOutput(filename, Context.MODE_PRIVATE);
   fos.write(string.getBytes());
   fos.close();
} catch (FileNotFoundException e) {
  // handle FileNotFoundException
} catch (IOException e) {
  // handle IOException
} finally {
  if (fos != null) {
    try {
      fos.close();
    } catch (IOException e) {
    }
  }
}

Related Vulnerabilities

• JVN#92038939 mixi for Android information management vulnerability
• JVN#05102851 Yome Collection for Android issue in management of IMEI

Related Guidelines

Bibliography