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 a flaw that allows an attacker to traverse outside of a restricted path. The issue is due to debug mode not properly sanitizing user input, specifically directory traversal style attacks (e.g., ../../) supplied via the adb Filename. This directory traversal attack would allow a physically present attacker to gain elevated privileges.
Android contains a flaw that may allow a malicious application to possess device administrator privileges but not appear on the list of applications which possess these privileges. This may be exploited to make it impossible to delete the malicious application.
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.