Multiple Android applications fail to properly validate SSL certificates

ID VU:582497
Type cert
Reporter CERT
Modified 2016-11-08T00:00:00



Multiple Android applications fail to properly validate SSL certificates provided by HTTPS connections, which may allow an attacker to perform a man-in-the-middle (MITM) attack.


When communicating via HTTPS, an application should validate the SSL chain to be sure that the certificate produced by the site was provided by a trusted root certificate authority (CA). Multiple Android applications fail to properly validate SSL certificates. Additional information can be found in the CERT Oracle Secure Coding Standard for Java:

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

Details of the methodology used to test applications with CERT Tapioca are described in the CERT/CC blog.

In March 2014 the Federal Trade Commission settled charges with two vendors (Fandango and Credit Karma) for failing to securely transmit sensitive personal information. An FTC press release states that "Consumers are increasingly using mobile apps for sensitive transactions. Yet research suggests that many companies, like Fandango and Credit Karma, have failed to properly implement SSL encryption."


An attacker on the same network as the Android device may be able to view or modify network traffic that should have been protected by HTTPS. The impact varies based on what the application is doing. Possible outcomes include credential stealing or arbitrary code execution.


Apply an update

Please refer to the Android application SSL spreadsheet for details about affected applications and the availability of fixes. If you are unable to view this document, a static copy of the spreadsheet is available here:

If fixes are not available for your application, please consider the following workarounds:

Do not use affected applications

Many Android applications are unnecessary in that the content they provide access to is available via other means. For example, while a bank may provide an Android application for accessing its resources, those same resources are usually available by using a web browser. By using a web browser to access those resources, you can help avoid situations where SSL may not be validated.

Avoid untrusted networks

Avoid using untrusted networks, including public WiFi. Using your device on an untrusted network increases the chance of falling victim to a MITM attack.

Vendor Information

Due to the number of affected applications, tested applications, versions, CVE identifiers, CERT VU# identifiers and other information will be available in the spreadsheet Android App SSL Failures. This spreadsheet will be kept up to date with newly-discovered vulnerable applications, fixed versions, manual testing notes, and other information.

The vendors listed below are simply vendors that operate Android application stores. We notified these vendors to mention the testing that we are performing and also suggest that similar testing could be used at the point where an application is tested for suitability for inclusion in their respective application stores.

Vendor| Status| Date Notified| Date Updated
Amazon| | 06 Aug 2014| 06 Aug 2014
Fortinet, Inc.| | 09 Jan 2014| 05 Jan 2015
Google| | 05 Aug 2014| 05 Aug 2014
PNC Bank| | 01 Oct 2014| 01 Oct 2014
Windstream| | 09 Jan 2014| 05 Jan 2015
If you are a vendor and your product is affected, let us know.

CVSS Metrics

Group | Score | Vector
Base | 7.8 | AV:A/AC:L/Au:N/C:C/I:C/A:N
Temporal | 7.0 | E:F/RL:W/RC:C
Environmental | 7.5 | CDP:ND/TD:H/CR:H/IR:H/AR:ND


  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>
  • <>


This vulnerability was reported by Will Dormann of the CERT/CC. Additional reporters of the concept of Android apps that fail to validate SSL certificates include Tony Trummer, Tushar Dalvi, and Kuo Chiang. Other individuals that publicly reported this issue include: Sascha Fahl, Marian Harbach,Thomas Muders, Matthew Smith, Lars Baumgärtner, and Bernd Freisleben.

This document was written by Will Dormann.

Other Information

  • CVE IDs: Unknown
  • Date Public: 16 Oct 2012
  • Date First Published: 03 Sep 2014
  • Date Last Updated: 08 Nov 2016
  • Document Revision: 31