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

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.

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

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):

• A vulnerability in Android Runtime could allow for remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. (CVE-2023-21265)
• A vulnerability in Framework that could allow for remote code execution. (CVE-2023-21287)
• 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)
  Details of lower-severity vulnerabilities are as follows:
• Multiple vulnerabilities in Framework that could allow for escalation of privilege. (CVE-2023-21287, CVE-2023-21269, CVE-2023-21270, CVE-2023-21272, CVE-2023-21278, CVE-2023-21281, CVE-2023-21286)
• Multiple vulnerabilities in Framework that could allow for denial of service. (CVE-2023-21280, CVE-2023-21284)
• Multiple vulnerabilities in Framework that could allow for information disclosure. (CVE-2023-21267, CVE-2023-21276, CVE-2023-21277, CVE-2023-21279, CVE-2023-21283, CVE-2023-21288, CVE-2023-21289, CVE-2023-21292)
• Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2023-20965, CVE-2023-21132, CVE-2023-21133, CVE-2023-21134, CVE-2023-21140, CVE-2023-21142, CVE-2023-21175)
• Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2023-21271, CVE-2023-21274, CVE-2023-21285)
• Multiple vulnerabilities in System that could allow for denial of service. (CVE-2023-21268, CVE-2023-21290)
• 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)
• A vulnerability in Arm components. (CVE-2022-34830)
• A vulnerability in MediaTek components. (CVE-2023-20780)
• Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2022-40510, CVE-2023-21626, CVE-2023-22666, CVE-2023-28537, CVE-2023-28555)
  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.

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)
  o 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.
  o 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.
  o 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.
  o 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.
  o 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.
  o 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.
  o 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.
  o 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)
  o 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.
  o 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)
  o 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™.
  o Safeguard 13.10 : Perform Application Layer Filtering: Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or gateway