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

MS-ISAC ADVISORY NUMBER:

2020-148

DATE(S) ISSUED:

11/03/2020

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.

THREAT INTELLIGENCE:

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

RISK:

Government:
  • Large and medium government entities: HIGH
  • Small government entities: HIGH
Businesses:
  • Large and medium business entities: HIGH
  • Small business entities: HIGH
Home Users:
HIGH

TECHNICAL SUMMARY:

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:

  • A denial of service vulnerability in System. (CVE-2020-0437)
  • An arbitrary code vulnerability in System. (CVE-2020-0449)
  • An elevation of privilege vulnerability in System. (CVE-2020-12856)
  • Multiple information disclosure vulnerabilities in System. (CVE-2020-0424, CVE-2020-0448, CVE-2020-0450, CVE-2020-0453)
  • An elevation of privilege vulnerability in Android runtime. (CVE-2020-0409)
  • An elevation of privilege vulnerability in Media Framework. (CVE-2020-0438)
  • An information disclosure vulnerability in Media Framework. (CVE-2020-0451)
  • An arbitrary code vulnerability in Media Framework. (CVE-2020-0452)
  • An information disclosure vulnerability in Framework. (CVE-2020-0454)
  • Multiple denial of service vulnerabilities in Framework. (CVE-2020-0441, CVE-2020-0442, CVE-2020-0443)
  • Multiple elevation of privilege vulnerabilities in Framework. (CVE-2020-0418, CVE-2020-0439)
  • Multiple high severity vulnerabilities in MediaTek components. (CVE-2020-0445, CVE-2020-0446, CVE-2020-0447)
  • A Critical severity vulnerability in Qualcomm closed-source components (CVE-2020-3639,)
  • Multiple high severity vulnerabilities in Qualcomm closed-source components (CVE-2020-11123, CVE-2020-11127, CVE-2020-11168, CVE-2020-11175, CVE-2020-11184, CVE-2020-11193, CVE-2020-11196, CVE-2020-11205, CVE-2020-3632)

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.

RECOMMENDATIONS:

We recommend the following actions be taken:

  • Apply appropriate updates by Google Android or mobile carriers to vulnerable systems, immediately after appropriate testing.
  • 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:

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0409 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0418 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0424 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0437 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0438 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0439 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0441 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0442 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0443 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0445 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0446 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0447 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0448 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0449 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0450 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0451 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0452 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0453 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0454 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3632 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3639 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11123 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11127 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11168 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11175 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11184 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11193 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11196 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11205 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12856

Information Hub : Advisories


CONTROL: 1 --- ADVISORY CONTROL: 0
CONTROL: 2 --- ADVISORY CONTROL: 0

Pencil Blog post 03 Dec 2020
CONTROL: 3 --- ADVISORY CONTROL: 0
CONTROL: 4 --- ADVISORY CONTROL: 0