In several posts we have discussed about the improper validation of SSL certificates made by mobile devices, recently we mentioned the case of the Gmail app for iOS devices which, according to an expert at mobile security firm Lacoon, doesn’t perform the certificate pinning procedure when establishing a trusted connection to the service provider. The failure of the certificate pinning procedure exposes users to the risk of MitM attacks and consequent theft of sensitive information.
The CERT Coordination Center at Carnegie Mellon University (CERT/CC) has published a list of popular Android applications that don’t implement correctly the SSL certificate validation, and the problems is widespread.
Recently security experts at FireEye evaluated the level of security offered by 1,000 of the most popular free apps offered on Google Play, also in this case the results are shocking, 68% of the app doesn’t check server certificates and 77% ignores SSL errors. According to the CERT, the applications are using vulnerable libraries, such as the Flurry and Chartboost ad libraries, for this reason Android users are exposed to the risk of attacks. Despite FireEye notified the flaws to the developers the CERT pointed out that only a few companies took steps to secure their products.
On October 2013, German researchers Beekman and Thompson published a study that revealed that many applications failed to properly implement SSL exposing users to basic Man-In-The-Middle attacks. In 13,500 of the most popular free applications on Google Play at the time, 8% implemented a vulnerable SSL and some of them collected a substantial amount of personal information.
The CERT conduced a wide-scale automated dynamic tests on the most popular Android mobile apps, its experts used for the test the CERT Tapioca tool, which is “a network-layer man-in-the-middle (MITM) proxy VM that is based on UbuFuzz and is preloaded with mitmproxy.”
The tool allows experts checking for apps that fail to validate digital certificates and Investigating traffic of any http/https traffic. Differently from the past, the researchers at CERT will contact every development team which designed the application that fail the test, the scope is to make them aware of the vulnerability and to provide suggestion to fix them.
Here is where CERT’s work is providing value:
The CERT also made public a spreadsheet which contains the list of the tested applications, the test results and many other information, including the CVE identifiers (e.g. CVE-2014-6024, CVE-2014-6025, CVE-2014-5524) for the vulnerabilities discovered by its team.
CERT clarified that it has decided to publish the names of flawed apps without giving developers time to address the vulnerabilities because this move gives an advantage to the end-users.
“If an attacker is interested in performing MITM attacks, they’re already doing it. That cat is already out of the bag. They’ve likely set up a rogue access point and are already capturing all of the traffic that passes through it,” “If end users have vulnerable applications on their phones, knowing which applications are affected does give an advantage to the defenders. They can choose to uninstall vulnerable applications until fixes are available, or if they must, they can choose to use said applications only on trusted networks.” said CERT/CC vulnerability analyst Will Dormann.
The activity is very positive and according to the CERT, the experts will update continually VU#582497 and any resources that the document uses, they intend to work closely with authors to improve the security of the most popular app.
(Security Affairs – MITM , CERT, Mobile)
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.