Google Android contains a flaw in the PreferenceActivity class that leads to unauthorized privileges being gained. The issue is due to the :android:show_fragment intent extra allowing for arbitrary classes to be loaded. This may allow a local attacker to use a specially crafted application to load arbitrary classes and gain elevated privileges.
Android contains a flaw related to improper initialization of the underlying OpenSSL PRNG that is triggered when an application e.g. uses the Java Cryptography Architecture (JCA) for key generation, signing, or random number generation. This may result in non-cryptographically strong values being generated, which could allow attackers to have various impacts depending on the affected application (e.g. compromise a user's Bitcoin wallet).
The Android OS contains a flaw that is due to unsigned values in extracted ZIP files. With a specially crafted classes.dex file, a local attacker can bypass signature verification and replace classes.dex with a malicious version.
Android contains a flaw that is due to the program failing to properly restrict users from modifying APK code. This may allow a local attacker to change APK code without breaking an application's cryptographic signature and subvert legitimate applications into running malicious code.
Android contains an unspecified flaw that may allow a local attacker to modify the AndroidManifest.xml file and still have it be correctly processed by the smartphone, which may make identifying attacks which rely on manipulating this file more difficult.
Android has been reported to contain a flaw related to data storage. The issue is allegedly due to Android storing data insecurely, allowing for copied data (i.e. cloned) to be used by a second application, allowing for an authentication bypass. However, the analysis is based on having super-user privileges when performing testing, which would of course allow such data access. Subsequent dispute has clarified that the behavior originally demonstrated is expected.