Multiple Vulnerabilities in Google Android OS Could Allow for Remote Code Execution

ITS Advisory Number: 
2018-018
Date(s) Issued: 
Tuesday, February 6, 2018
Subject: 
Multiple Vulnerabilities in Google Android OS Could Allow for Remote Code Execution
Overview: 

Multiple vulnerabilities have been discovered in the Google Android operating system (OS), the most severe of which could allow for remote code execution. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution within the context of a privileged process. Depending on the privileges associated with this application, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

Systems Affected: 
  • Android OS builds utilizing Security Patch Levels issued prior to February 5, 2018.
RISK
GOVERNMENT
Large and medium government entities: 
High
Small government entities: 
High
BUSINESS
Large and medium business entities: 
High
Small business entities: 
High
Home Users: 
High
Description: 

Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for remote code execution within the context of a privileged process. Details of these vulnerabilities are as follows:

  • Multiple remote code execution vulnerabilities in Media Framework (CVE-2017-13228, CVE-2017-13230).
  • An information disclosure vulnerability in Media Framework (CVE-2017-13232).
  • An elevation of privilege vulnerability in Media Framework (CVE-2017-13231).
  • Multiple denial of service vulnerabilities in Media Framework (CVE-2017-13230, CVE-2017-13233, CVE-2017-13234).
  • An elevation of privilege vulnerability in System (CVE-2017-13236).
  • An information disclosure vulnerability in HTC components (CVE-2017-13238).
  • An elevation of privilege vulnerability in HTC components (CVE-2017-13247).
  • Multiple elevation of privilege vulnerabilities in Kernel components (CVE-2017-15265, CVE-2015-9016, CVE-2017-17770).
  • Multiple elevation of privilege vulnerabilities in NVIDIA components (CVE-2017-6279, CVE-2017-6258).
  • Multiple remote code execution vulnerabilities in Qualcomm components (CVE-2017-15817, CVE-2017-17760).
  • Multiple elevation of privilege vulnerabilities in Qualcomm components (CVE-2017-11041, CVE-2017-17767, CVE-2017-17765,  CVE-2017-17762, CVE-2017-14884, CVE-2017-15829, CVE-2017-15820, CVE-2017-17764, CVE-2017-17761).
  • A vulnerability in the Qualcomm closed-source components (CVE-2017-14910).

Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution in the context of a privileged process. These vulnerabilities could be exploited through multiple methods such as email, web browsing, and MMS when processing media files. Depending on the privileges associated with the application, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

Actions: 
  • After appropriate testing, immediately apply updates provided by Google Android or mobile carriers to vulnerable systems.
  • Remind users to only download applications from trusted vendors in the Play Store.
  • Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources.
  • Inform and educate users regarding threats posed by hypertext links contained in emails or attachments, especially from un-trusted sources.
References: 

Google Android:

https://source.android.com/security/bulletin/2018-02-01

CVE:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9016

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6258

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6279

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11041

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13228

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13230

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13231

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13232

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13233

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13234

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13236

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13238

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13247

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14884

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14910

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15265

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15817

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15820

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15829

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17760

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17761

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17762

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17764

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17765

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17767

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17770