CVE-2022-20058: Medium severity android vulnerability
Published Mar 9, 2022
·Updated
In preloader (usb), there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, for an attacker who has physical access to the device, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS06160806; Issue ID: ALPS06160485.
Affected Software
35 affected components
Google Android=10.0
Google Android=11.0
Google Android=12.0
MediaTek Mt6761
MediaTek Mt6762
MediaTek Mt6765
MediaTek Mt6768
MediaTek Mt6771
MediaTek Mt6779
MediaTek Mt6781
MediaTek Mt6785
MediaTek Mt6833
MediaTek Mt6853
MediaTek Mt6853t
MediaTek Mt6873
MediaTek Mt6877
MediaTek Mt6885
MediaTek Mt6893
MediaTek Mt8183
MediaTek Mt8185
MediaTek Mt8321
MediaTek Mt8385
MediaTek Mt8666
MediaTek Mt8667
MediaTek Mt8675
MediaTek Mt8735a
MediaTek Mt8735b
MediaTek Mt8765
MediaTek Mt8766
MediaTek Mt8768
MediaTek Mt8786
MediaTek Mt8788
MediaTek Mt8789
MediaTek Mt8791
MediaTek Mt8797
Event History
Mar 9, 2022
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the vulnerability ID of this issue?
The vulnerability ID is CVE-2022-20058.
2
What is the severity rating of CVE-2022-20058?
The severity rating of CVE-2022-20058 is medium.
3
What software versions are affected by CVE-2022-20058?
Google Android versions 10.0, 11.0, and 12.0 are affected by CVE-2022-20058.
4
How can an attacker exploit CVE-2022-20058?
An attacker with physical access to the device would need user interaction to exploit CVE-2022-20058.
5
Is Mediatek Mt6761 vulnerable to CVE-2022-20058?
No, Mediatek Mt6761 is not vulnerable to CVE-2022-20058.