CVE-2022-20012: Integer Overflow
First published: Tue Jan 04 2022(Updated: )
In mdp driver, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05836478; Issue ID: ALPS05836478.
Credit: security@mediatek.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Android | =10.0 | |
| Google Android | =11.0 | |
| Google Android | =12.0 | |
| Mediatek Mt6580 | ||
| Mediatek Mt6739 | ||
| Mediatek Mt6750 | ||
| Mediatek Mt6750s | ||
| Mediatek Mt6753 | ||
| Mediatek Mt6755 | ||
| Mediatek Mt6757 | ||
| Mediatek Mt6761 | ||
| Mediatek Mt6762 | ||
| Mediatek Mt6765 | ||
| Mediatek Mt6768 | ||
| Mediatek Mt6769 | ||
| Mediatek Mt6771 | ||
| Mediatek Mt6779 | ||
| Mediatek Mt6785 | ||
| Mediatek Mt6833 | ||
| Mediatek Mt6853 | ||
| Mediatek Mt6853t | ||
| Mediatek Mt6873 | ||
| Mediatek Mt6875 | ||
| Mediatek Mt6877 | ||
| Mediatek Mt6883 | ||
| Mediatek Mt6885 | ||
| Mediatek Mt6889 | ||
| Mediatek Mt6891 | ||
| Mediatek Mt6893 | ||
| Mediatek Mt8127 | ||
| Mediatek Mt8163 | ||
| Mediatek Mt8167 | ||
| Mediatek Mt8168 | ||
| Mediatek Mt8169 | ||
| Mediatek Mt8173 | ||
| Mediatek Mt8183 | ||
| Mediatek Mt8188 | ||
| Mediatek Mt8195 | ||
| Mediatek Mt8321 | ||
| Mediatek Mt8362a | ||
| Mediatek Mt8365 | ||
| Mediatek Mt8385 | ||
| Mediatek Mt8765 | ||
| Mediatek Mt8788 |
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 of this vulnerability?
The vulnerability ID of this vulnerability is CVE-2022-20012.
What is the severity of CVE-2022-20012?
The severity of CVE-2022-20012 is high with a CVSS score of 7.8.
What is the affected software?
The affected software includes Google Android versions 10.0, 11.0, and 12.0.
Is user interaction required for exploitation of CVE-2022-20012?
No, user interaction is not needed for exploitation of CVE-2022-20012.
How can I fix CVE-2022-20012?
To fix CVE-2022-20012, apply the patch with ID ALPS05836478 provided by Mediatek.
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/references
- agent/weakness
- agent/severity
- agent/author
- 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 mt6580
- canonical/mediatek mt6739
- canonical/mediatek mt6750
- canonical/mediatek mt6750s
- canonical/mediatek mt6753
- canonical/mediatek mt6755
- canonical/mediatek mt6757
- canonical/mediatek mt6761
- canonical/mediatek mt6762
- canonical/mediatek mt6765
- canonical/mediatek mt6768
- canonical/mediatek mt6769
- canonical/mediatek mt6771
- canonical/mediatek mt6779
- canonical/mediatek mt6785
- canonical/mediatek mt6833
- canonical/mediatek mt6853
- canonical/mediatek mt6853t
- canonical/mediatek mt6873
- canonical/mediatek mt6875
- canonical/mediatek mt6877
- canonical/mediatek mt6883
- canonical/mediatek mt6885
- canonical/mediatek mt6889
- canonical/mediatek mt6891
- canonical/mediatek mt6893
- canonical/mediatek mt8127
- canonical/mediatek mt8163
- canonical/mediatek mt8167
- canonical/mediatek mt8168
- canonical/mediatek mt8169
- canonical/mediatek mt8173
- canonical/mediatek mt8183
- canonical/mediatek mt8188
- canonical/mediatek mt8195
- canonical/mediatek mt8321
- canonical/mediatek mt8362a
- canonical/mediatek mt8365
- canonical/mediatek mt8385
- canonical/mediatek mt8765
- canonical/mediatek mt8788