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

ITS Advisory Number: 
2017-121
Date(s) Issued: 
Tuesday, December 5, 2017
Subject: 
Multiple Vulnerabilities in Google Android OS Could Allow for Arbitrary Code Execution
Overview: 

Multiple vulnerabilities have been discovered in Google Android operating system (OS), the most severe of which could allow for arbitrary 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 arbitrary 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 December 5, 2017
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 arbitrary code execution within the context of a privileged process. Details of these vulnerabilities are as follows:

  • Multiple elevation of privilege vulnerabilities in Framework. (CVE-2017-0807, CVE-2017-0870, CVE-2017-0871)
  • Multiple elevation of privilege vulnerabilities in Kernel components. (CVE-2017-0564, CVE-2017-13162, CVE-2017-13174, CVE-2017-7533)
  • Multiple elevation of privilege vulnerabilities in Media framework. (CVE-2017-0837, CVE-2017-13153)
  • Multiple arbitrary code execution vulnerabilities in Media framework. (CVE-2017-0872, CVE-2017-0876, CVE-2017-0877, CVE-2017-0878, CVE-2017-13151)
  • Multiple denial of service vulnerabilities in Media framework. (CVE-2017-0873, CVE-2017-0874, CVE-2017-0880, CVE-2017-13148)
  • Multiple elevation of privilege vulnerabilities in MediaTek components. (CVE-2017-13170, CVE-2017-13171, CVE-2017-13173)
  • Multiple elevation of privilege vulnerabilities in NVIDIA components. (CVE-2017-6262, CVE-2017-6263, CVE-2017-6276)
  • Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2017-11005, CVE-2017-14908, CVE-2017-14909, CVE-2017-14914, CVE-2017-14916, CVE-2017-14917, CVE-2017-14918, CVE-2017-6211)
  • Multiple arbitrary code execution vulnerabilities in Qualcomm components. (CVE-2016-3706, CVE-2016-4429, CVE-2017-11043)
  • Multiple elevation of privilege vulnerabilities in Qualcomm components. (CVE-2017-11007, CVE-2017-14895, CVE-2017-14897, CVE-2017-14902, CVE-2017-14904, CVE-2017-9716)
  • An elevation of privilege vulnerability in System. (CVE-2017-13156)
  • Multiple information disclosure vulnerabilities in System. (CVE-2017-13157, CVE-2017-13158, CVE-2017-13159)
  • An arbitrary code execution vulnerability in System. (CVE-2017-13160)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary 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. 

THREAT INTELLIGENCE:

There are currently no reports of these vulnerabilities being exploited in the wild

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:

http://source.android.com/security/bulletin/2017-12-01

CVE:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3706

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4429

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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