Please ensure Javascript is enabled for purposes of website accessibility
Portal oficial del Gobierno de Puerto Rico. 
Un sitio web oficial .pr.gov pertenece a una organización oficial del Gobierno de Puerto Rico.
Los sitios web seguros .pr.gov usan HTTPS, lo que significa que usted se conectó de forma segura a un sitio web.

TECNOLOGÍA

Gobierno de Puerto Rico

Alerta de ciberseguidad

Puerto Rico Innovation & Technology Service

Date:

June 5, 2023

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

Gobierno:
High
Medium
Low
Negocios:
High
Medium
Low
Hogar:
High
Medium
Low

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 privilege escalation. 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 currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED:

  • Android OS patch levels prior to 2023-06-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: Remote Code Execution  (T1203):

  • Multiple vulnerabilities in System that could allow for remote code execution. (CVE-2023-21108, CVE-2023-21130)
  • A vulnerability in Framework that could allow for remote code execution. (CVE-2023-21127)

Details of lower-severity vulnerabilities are as follows:

  • Multiple vulnerabilities in Framework that could allow for escalation of privilege. (CVE-2023-21126, CVE-2023-21128, CVE-2023-21129, CVE-2023-21131, CVE-2023-21139)
  • Multiple vulnerabilities in Framework that could allow for denial of service. (CVE-2023-21136, CVE-2023-21137, CVE-2023-21143)
  • A vulnerability in Framework that could allow for information disclosure. (CVE-2023-21105)
  • Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2023-21115, CVE-2023-21121, CVE-2023-21122, CVE-2023-21123, CVE-2023-21124, CVE-2023-21135, CVE-2023-21138)
  • Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2023-21095, CVE-2023-21141, CVE-2023-21142)
  • Multiple vulnerabilities in System that could allow for denial of service. (CVE-2023-21144)
  • Multiple vulnerabilities in Arm components. (CVE-2022-22706, CVE-2022-28349, CVE-2022-46781)
  • Multiple vulnerabilities in Imagination Technologies (CVE-2021-0701, CVE-2021-0945).
  • Multiple vulnerabilities in Unisoc components. (CVE-2022-48390, CVE-2022-48392, CVE-2022-48438, CVE-2022-48391)
  • Multiple Vulnerabilities in Widevine DRM. (CVE-2023-21101, CVE-2023-21120)
  • Multiple vulnerabilities in Qualcomm components (CVE-2022-33292, CVE-2023-21656, CVE-2023-21657, CVE-2023-21669, CVE-2023-21670)
  • Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2022-33257, CVE-2022-40529, CVE-2022-22060, CVE-2022-33251, CVE-2022-33264, CVE-2022-40516, CVE-2022-40517, CVE-2022-40520, CVE-2022-40521, CVE-2022-40523, CVE-2022-40533, CVE-2022-40536, CVE-2022-40538, CVE-2023-21628, CVE-2023-21658, CVE-2023-21659, CVE-2023-21661)

Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation. 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 appropriate patches provided by Google or phone vendor 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.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
  • Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
  • 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. (M1017: User Training)
  • 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 Apple® System Integrity Protection (SIP) and Gatekeeper™.

REFERENCES:

Google:
https://source.android.com/docs/security/bulletin/2023-06-01#2023-06-05-security-patch-level-vulnerability-details

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-0701
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-0945
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22060
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22706
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28349
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33251
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33257
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33264
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33292
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40516
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40517
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40520
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40521
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40523
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40529
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40533
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40536
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40538
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46781
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48390
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48391
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48392
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48438
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21095
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21101
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21105
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21108
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21115
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21120
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21121
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21122
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21123
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21124
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21126
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21127
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21128
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21129
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21130
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21131
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21135
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21136
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21137
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21138
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21139
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21141
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21142
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21143
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21144
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21628
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21656
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21657
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21658
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21659
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21661
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21669
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21670