Advisory

Yorick Koster, April 2014

Outlook.com for Android fails to validate server certificates

Abstract

Outlook.com for Android's WebView contains an insecure SSL error handler that ignores any certificate validation errors. Due to this, it is possible to perform a man in the middle attack against this app. The vulnerable component is used to log into outlook.com. A successful attack allows sniffing of login credentials (user name & password).

Outlook.com for Android fails to validate server certificates from Securify BV on Vimeo.

Tested versions

This issue was found in Outlook.com for Android version 7.8.2.12.49.2176 and version 7.8.2.12.49.6434.

See also

- CVE-2014-5239
- JVNDB-2014-000086 Outlook.com for Android contains an issue where it fails to verify SSL server certificates

Fix

A new version (7.8.2.12.49.7090) of Outlook.com for Android was released in which the affected SSL error handler is no longer present. The latest version of Outlook.com for Android can be obtained from Google Play

Introduction

When logging into outlook.com, Outlook.com for Android will load login.live.com in a WebView. This WebView has implemented a custom SSL error handler, which basically ignores any certificate validation errors.

Insecure error handler

The affected SSL error handler can be found in the AuthorizationWebViewClient inner class of com.microsoft.live.AuthorizationRequest$OAuthDialog. The relevant code is listed below.

public void onReceivedSslError(WebView paramWebView, SslErrorHandler paramSslErrorHandler, SslError paramSslError)
{
      AuthorizationRequest.OAuthDialog.this.setLiveSdkProvProgressStatus(false);
      paramSslErrorHandler.proceed();
}

As can be seen in this listing, the method gets an SslErrorHandler instance named paramSslErrorHandler. The handler calls proceed(), which will ignore any certificate error and the connection will be created. Due to this, any invalid certificate will also be accepted, even the attacker's certificate rendering the app vulnerable to man in the middle attacks. Since this issue exists within a login component, it is possible to steal Microsoft account login credentials, which is usually an Outlook.com email address and password.

Work with us →