CVE-2022-20060
First published: Wed Mar 09 2022(Updated: )
In preloader (usb), there is a possible permission bypass due to a missing proper image authentication. 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: ALPS06137462.
Credit: security@mediatek.com security@mediatek.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 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 Mt6873 | ||
| Mediatek Mt6875 | ||
| Mediatek Mt6877 | ||
| Mediatek Mt6885 | ||
| Mediatek Mt6889 | ||
| 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 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-20060.
What is the severity of CVE-2022-20060?
The severity of CVE-2022-20060 is medium (6.6).
How does CVE-2022-20060 occur?
CVE-2022-20060 occurs due to a missing proper image authentication in preloader (usb), which can lead to local escalation of privilege.
Which software versions are affected by CVE-2022-20060?
Google Android versions 10.0, 11.0, and 12.0 are affected by CVE-2022-20060.
How can CVE-2022-20060 be fixed?
To fix CVE-2022-20060, it is recommended to apply the necessary patches and updates provided by the software vendor.
- agent/author
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- agent/references
- agent/weakness
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- vendor/google
- canonical/google android
- version/google android/10.0
- version/google android/11.0
- version/google android/12.0
- vendor/mediatek
- canonical/mediatek mt6761
- canonical/mediatek mt6762
- canonical/mediatek mt6765
- canonical/mediatek mt6768
- canonical/mediatek mt6771
- canonical/mediatek mt6779
- canonical/mediatek mt6781
- canonical/mediatek mt6785
- canonical/mediatek mt6833
- canonical/mediatek mt6853
- canonical/mediatek mt6873
- canonical/mediatek mt6875
- canonical/mediatek mt6877
- canonical/mediatek mt6885
- canonical/mediatek mt6889
- canonical/mediatek mt6893
- canonical/mediatek mt8183
- canonical/mediatek mt8185
- canonical/mediatek mt8321
- canonical/mediatek mt8385
- canonical/mediatek mt8666
- canonical/mediatek mt8667
- canonical/mediatek mt8675
- canonical/mediatek mt8735a
- canonical/mediatek mt8735b
- canonical/mediatek mt8765
- canonical/mediatek mt8766
- canonical/mediatek mt8768
- canonical/mediatek mt8786
- canonical/mediatek mt8788
- canonical/mediatek mt8789
- canonical/mediatek mt8791
- canonical/mediatek mt8797