<
>

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 https://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 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 December 2, 2019.

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 arbitrary code execution within the context of a privileged process. Details of these vulnerabilities are as follows:

  • Multiple denial of service vulnerabilities in Framework. (CVE-2018-11980, CVE-2018-20961, CVE-2019-10480, CVE-2019-10481, CVE-2019-10482, CVE-2019-10487, CVE-2019-10500, CVE-2019-10513, CVE-2019-10516, CVE-2019-10517, CVE-2019-10525, CVE-2019-10536, CVE-2019-10537, CVE-2019-10557, CVE-2019-10595, CVE-2019-10598, CVE-2019-10601, CVE-2019-10605, CVE-2019-10607, CVE-2019-15220, CVE-2019-15239, CVE-2019-2217, CVE-2019-2218, CVE-2019-2219, CVE-2019-2220, CVE-2019-2221, CVE-2019-2222, CVE-2019-2223, CVE-2019-2224, CVE-2019-2225, CVE-2019-2226, CVE-2019-2227, CVE-2019-2228, CVE-2019-2229, CVE-2019-2230, CVE-2019-2231, CVE-2019-2232, CVE-2019-2242, CVE-2019-2274, CVE-2019-2304, CVE-2019-9464)
  • Multiple elevation of privilege vulnerabilities in Framework. (CVE-2019-2217, CVE-2019-2218, CVE-2019-2221, CVE-2019-9464)
  • Multiple information disclosure vulnerabilities in Framework. (CVE-2019-2219, CVE-2019-2220)
  • Multiple elevation of privilege vulnerabilities in Kernel components. (CVE-2018-20961, CVE-2019-15220, CVE-2019-15239)
  • Multiple arbitrary code vulnerabilities in Media framework. (CVE-2019-2222, CVE-2019-2223)
  • Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2019-10482, CVE-2019-10487, CVE-2019-10500, CVE-2019-10513, CVE-2019-10516, CVE-2019-10517, CVE-2019-10525, CVE-2019-2242, CVE-2019-2274)
  • Multiple vulnerabilities in Qualcomm components. (CVE-2019-10481, CVE-2019-10537, CVE-2019-10557, CVE-2019-2304)
  • An arbitrary code vulnerability in System. (CVE-2019-2224)
  • An elevation of privilege vulnerability in System. (CVE-2019-2225)
  • Multiple information disclosure vulnerabilities in System. (CVE-2019-2226, CVE-2019-2227, CVE-2019-2228, CVE-2019-2229, CVE-2019-2230, CVE-2019-2231)

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.

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:

Google Android:

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

CVE:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11980
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20961
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20961
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2217
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2217
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2218
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2219
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2219
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2220
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2221
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2222
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2222
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2223
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2224
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2224
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2225
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2225
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2226
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2226
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2227
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2228
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2229
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2230
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2231
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2232
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2242
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2274
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2304
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9464
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10480
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10481
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10481
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10482
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10482
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10487
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10500
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10513
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10516
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10517
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10525
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10536
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10537
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10557
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10595
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10598
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10601
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10605
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10607
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15220
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15239

You might also like
Most comment
share us your thought

0 Comment Log in or register to post comments