Multiple Vulnerabilities in Google Android OS Could Allow for Remote Code Execution
ITS ADVISORY NUMBER:
2023-117
DATE(S) ISSUED:
10/11/2023
SUBJECT:
Multiple Vulnerabilities in Google Android OS Could Allow for Remote Code Execution
OVERVIEW:
Multiple vulnerabilities have been discovered in Google Android 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. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
THREAT INTELLIGENCE:
There are reports of these vulnerabilities being exploited in the wild. (CVE-2023-4863, CVE-2023-4211)
SYSTEMS AFFECTED:
- Android OS patch levels prior to 2023-10-05
RISK:
Government:
- Large and medium government entities: High
- Small government entities: Medium
Businesses:
- Large and medium business entities: High
- Small business entities: Medium
Home users: Low
TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for remote code execution in the context of the affected component. Following the MITRE ATT&CK framework, exploitation of these vulnerabilities can be classified as follows:
Tactic: Execution (TA0002)
Technique: Exploitation for Client Execution (T1203):
- Multiple vulnerabilities in System that could allow for remote code execution. (CVE-2023-40129, CVE-2023-4863)
- A vulnerability in Media Framework that could allow for remote code execution. (CVE-2023-21282)
- A vulnerability in System that could allow for remote code execution. (CVE-2023-21273)
- Multiple vulnerabilities in Qualcomm closed-source components that could allow for remote code execution. (CVE-2023-24855, CVE-2023-28540, CVE-2023-33028)
Details of lower-severity vulnerabilities are as follows:
- Multiple vulnerabilities in Framework that could allow for escalation of privilege. (CVE-2023-21266, CVE-2023-40116, CVE-2023-40120, CVE-2023-40131, CVE-2023-40140)
- Multiple vulnerabilities in Framework that could allow for information disclosure. (CVE-2023-21291, CVE-2023-40121, CVE-2023-40134, CVE-2023-40136, CVE-2023-40137, CVE-2023-40138, CVE-2023-40139)
- Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2023-21244, CVE-2023-40117, CVE-2023-40125, CVE-2023-40128, CVE-2023-40130 )
- Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2023-40123, CVE-2023-40127, CVE-2023-40133, CVE-2023-40135)
- Multiple vulnerabilities in System that could allow for denial of service. (CVE-2023-21252 , CVE-2023-21253)
- Multiple vulnerabilities in Project Mainline components. (CVE-2023-21282, CVE-2023-21132, CVE-2023-21133, CVE-2023-21134, CVE-2023-21140, CVE-2023-20965, CVE-2023-21242)
- Multiple vulnerabilities in Kernel that could allow for escalation of privilege. (CVE-2023-21264, CVE-2020-29374)
- Multiple vulnerabilities in Arm components. (CVE-2021-44828, CVE-2022-28348, CVE-2023-4211, CVE-2023-33200, CVE-2023-34970)
- Multiple vulnerabilities in MediaTek components. (CVE-2023-20819, CVE-2023-32819, CVE-2023-32820)
- A vulnerability in Unisoc components. (CVE-2023-40638)
- Multiple vulnerabilities in Qualcomm components. (CVE-2023-33029, CVE-2023-33034, CVE-2023-33035)
- Multiple vulnerabilities in Qualcomm closed-source components (CVE-2023-21673, CVE-2023-22385, CVE-2023-24843, CVE-2023-24844, CVE-2023-24847, CVE-2023-24848, CVE-2023-24849, CVE-2023-24850, CVE-2023-24853, CVE-2023-33026, CVE-2023-33027)
Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
- Apply the stable channel update provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
- Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
- Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
- Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
- Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)
- Safeguard 4.1 : Establish and Maintain a Secure Configuration Process: Establish and maintain a secure configuration process for enterprise assets (end-user devices, including portable and mobile, non-computing/IoT devices, and servers) and software (operating systems and applications). Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 16.8: Separate Production and Non-Production Systems: Maintain separate environments for production and non-production systems.
- Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
Safeguard 13.10 : Perform Application Layer Filtering: Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or gateway.
REFERENCES:
Google:
https://source.android.com/docs/security/bulletin/2023-10-01
MediaTek:
https://corp.mediatek.com/product-security-bulletin/October-2023
Unisoc:
https://www.cybersecurity-help.cz/vdb/SB2023100252
Qualcomm:
https://docs.qualcomm.com/product/publicresources/securitybulletin/october-2023-bulletin.html
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29374
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44828
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4211
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4863
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28348
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-20819
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-20965
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21132
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21133
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21134
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21140
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21242
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21244
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21252
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21253
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21264
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21266
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21273
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21282
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21291
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21673
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22385
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24843
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24844
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24848
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24849
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24850
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24853
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24855
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28540
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32819
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32820
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33026
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33027
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33028
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33029
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33034
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33035
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33200
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34970
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40116
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40117
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40120
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40121
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40123
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40125
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40127
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40128
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40129
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40130
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40131
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40133
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40134
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40135
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40136
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40137
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40138
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40139
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40140
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40638
TLP:CLEAR
www.cisa.gov/tlp