<
>

CyberSecurity Asean security alert on Multiple Vulnerabilities in Google Android OS Could Allow for Arbitrary Code Execution

This alert is originally published and can be viewed at www.cisecurity.org

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 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.

SYSTEMS AFFECTED:

  • Android OS builds utilizing Security Patch Levels issued prior to February 5, 2019

RISK:
Government:

  • Large and medium government entities: N/A

  • Small government entities: N/A

Businesses:

  • Large and medium business entities: N/A

  • Small business entities: N/A

Home Users:
N/A

TECHNICAL SUMMARY:
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 remote code execution vulnerabilities in Framework. (CVE-2019-1986, CVE-2019-1987, CVE-2019-1988)

  • Multiple remote code execution vulnerabilities in Library. (CVE-2017-17760, CVE-2018-5268, CVE-2018-5269)

  • An information disclosure vulnerability in Library. (CVE-2017-18009)

  • Multiple remote code execution vulnerabilities in System. (CVE-2019-1991, CVE-2019-1992)

  • Multiple elevation of privilege vulnerabilities in System. (CVE-2019-1993, CVE-2019-1994)

  • Multiple information disclosure vulnerabilities in System. (CVE-2019-1995, CVE-2019-1996, CVE-2019-1997)

  • A denial of service vulnerability in System. (CVE-2019-1998)

  • Multiple elevation of privilege vulnerabilities in Kernel components. (CVE-2018-10879, CVE-2019-1999, CVE-2019-2000)

  • An information disclosure vulnerability in Kernel components. (CVE-2019-2001)

  • A remote code execution vulnerability in NVIDIA components. (CVE-2018-6271)

  • An elevation of privilege vulnerability in NVIDIA components. (CVE-2018-6267, CVE-2018-6268)

  • An information disclosure vulnerability in NVIDIA components. (CVE-2016-6684)

  • Multiple vulnerabilities in Qualcomm components. (CVE-2018-11262, CVE-2018-11280, CVE-2018-11275, CVE-2018-13900, CVE-2018-13905)

  • Multiple Qualcomm closed-source components. (CVE-2018-11289, CVE-2018-11820, CVE-2018-11938, CVE-2018-11945, CVE-2018-11268, CVE-2018-11845, CVE-2018-11864, CVE-2018-11921, CVE-2018-11931, CVE-2018-11932, CVE-2018-11935, CVE-2018-11948, CVE-2018-5839, CVE-2018-13904)

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.

RECOMENDATIONS:
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:
Google Android:
https://source.android.com/security/bulletin/2019-02-01.html
CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6684http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17760http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18009http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10879http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11262http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11268http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11275http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11280http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11289http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11820http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11845http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11864http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11921http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11931http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11932http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11935http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11938http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11945http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11948http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13900http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13904http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13905http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5268http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5269http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5839http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6267http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6268http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6271http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1986http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1987http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1988http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1991http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1992http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1993http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1994http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1995http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1996http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1997http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1998http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1999http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2000http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2001

You might also like
Most comment
share us your thought

0 Comment Log in or register to post comments