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

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

Multiple vulnerabilities have been discovered in the 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.

 

THREAT INTELLIGENCE:

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

Systems Affected: 
  • Android OS builds utilizing Security Patch Levels issued prior to March 4, 2019.

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 vulnerabilities in Framework could allow for escalation of privilege (CVE-2018-20346, CVE-2019-1985, CVE-2019-2003, CVE-2019-2005).

  • A vulnerability in Framework that could allow for information disclosure (CVE-2019-2004).

  • Multiple vulnerabilities in Media framework that could allow for remote code execution (CVE-2019-1989, CVE-2019-1990).

  • Multiple vulnerabilities in Media framework that could allow for escalation of privilege (CVE-2019-2006, CVE-2019-2007, CVE-2019-2008).

  • A vulnerability in System that could allow for remote code execution (CVE-2019-2009).

  • Multiple vulnerabilities in System that could allow for escalation of privilege (CVE-2019-2010, CVE-2019-2011, CVE-2019-2012, CVE-2019-2013, CVE-2019-2014, CVE-2019-2015, CVE-2019-2016, CVE-2019-2017, CVE-2019-2018, CVE-2019-2023).

  • Multiple vulnerabilities in System that could allow for information disclosure (CVE-2018-9561, CVE-2018-9563, CVE-2018-9564, CVE-2019-2019, CVE-2019-2020, CVE-2019-2021, CVE-2019-2022).

  • Multiple vulnerabilities in Kernel components could allow for escalation of privilege (CVE-2018-10883, CVE-2019-2024, CVE-2019-2025).

  • Multiple Critical severity vulnerabilities in Qualcomm components (CVE-2017-8252, CVE-2018-11817, CVE-2018-11817).

  • Multiple High severity vulnerabilities in Qualcomm components (CVE-2018-13899, CVE-2018-13917).

  • Multiple Critical severity vulnerabilities in Qualcomm closed-source components (CVE-2017-8252, CVE-2018-11958).

  • Multiple High severity vulnerabilities in Qualcomm closed-source components (CVE-2018-11966, CVE-2018-11970, CVE-2018-11971, CVE-2018-13918). 

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.

Actions: 
  • After appropriate testing, immediately apply updates 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/2019-03-01

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8252
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10883
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11817
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11958
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11966
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11970
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11971
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13899
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13917
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13918
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20346
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9561
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9563
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9564
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1985
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1989
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1990
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2003
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2004
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2005
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2006
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2007
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2008
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2009
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2010
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2011
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2012
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2013
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2014
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2015
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2016
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2017
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2018
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2019
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2020
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2021
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2022
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2023
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2024
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2025