CVE-2021-30521: Heap buffer overflow in Autofill
Published May 13, 2021
·Updated
Heap buffer overflow in Autofill in Google Chrome on Android prior to 91.0.4472.77 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page.
Credit
ZhanJia Song
Affected Software
5 affected componentsFixes available
Google Chrome<91.0.4472.77
91.0.4472.77
Google Chrome<91.0.4472.77
Google Android
fedoraproject fedora=33
fedoraproject fedora=34
Remediation
Patch Available
Event History
May 13, 2021
CVE Published
12:00 AM
Jun 7, 2021
CVE Published
via MITRE·07:25 PM
Data Sourced
via MITRE·07:25 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2021-30522
- CVE-2021-30523
- CVE-2021-30524
- CVE-2021-30525
- CVE-2021-30526
- CVE-2021-30527
- CVE-2021-30528
- CVE-2021-4322
- CVE-2021-30529
- CVE-2021-30530
- CVE-2021-30531
- CVE-2021-30532
- CVE-2021-30533
- CVE-2021-30534
- CVE-2021-30535
- CVE-2021-30542
- CVE-2021-30543
- CVE-2021-30558
- CVE-2021-30536
- CVE-2021-30537
- CVE-2021-30538
- CVE-2021-30539
- CVE-2021-30540
- CVE-2021-4321
Frequently Asked Questions
1
What is the severity of CVE-2021-30521?
CVE-2021-30521 is considered a high-severity vulnerability due to the potential for remote code execution.
2
How do I fix CVE-2021-30521?
To fix CVE-2021-30521, update Google Chrome to version 91.0.4472.77 or later.
3
Who is affected by CVE-2021-30521?
CVE-2021-30521 affects users of Google Chrome on Android devices running versions prior to 91.0.4472.77.
4
What type of vulnerability is CVE-2021-30521?
CVE-2021-30521 is classified as a heap buffer overflow vulnerability.
5
Can exploiting CVE-2021-30521 lead to data theft?
Yes, exploiting CVE-2021-30521 could potentially allow attackers to access sensitive data on affected devices.