CVE-2011-3918: High severity android vulnerability
Published Oct 7, 2012
·Updated
The Zygote process in Android 4.0.3 and earlier accepts fork requests from processes with arbitrary UIDs, which allows remote attackers to cause a denial of service (reboot loop) via a crafted application.
Affected Software
32 affected components
Google Android=2.2.3
Google Android=2.0.1
Google Android=1.0
Google Android=3.2.6
Google Android=1.6
Google Android=2.1
Google Android=3.2.4
Google Android=3.2
Google Android=3.2.2
Google Android=4.0.2
Google Android=2.3-rev1
Google Android=2.3.6
Google Android=4.0.1
Google Android=2.3.3
Google Android=3.0
Google Android=2.0
Google Android=2.3.1
Google Android=2.3.5
Google Android=1.5
Google Android=3.1
Google Android=2.2.1
Google Android=2.2.2
Google Android=2.2
Google Android=2.3.4
Google Android=4.0
Google Android=2.3.7
Google Android=2.2-rev1
Google Android=1.1
Google Android=2.3.2
Google Android=3.2.1
Google Android=2.3
Google Android<=4.0.3
Event History
Oct 7, 2012
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2011-3918?
CVE-2011-3918 has a severity rating of high due to its potential to cause a denial of service through a reboot loop.
2
How do I fix CVE-2011-3918?
To fix CVE-2011-3918, update your Android device to a version later than 4.0.3 or apply any available security patches.
3
What versions of Android are affected by CVE-2011-3918?
CVE-2011-3918 affects Android versions up to 4.0.3, including 1.0 to 4.0.2.
4
Can CVE-2011-3918 be exploited remotely?
Yes, CVE-2011-3918 can be exploited remotely via a crafted application that triggers fork requests.
5
What impact does CVE-2011-3918 have on Android devices?
CVE-2011-3918 can lead to a denial of service by causing affected Android devices to enter a reboot loop.