A security flaw has allegedly been discovered in the APK code of android-powered devices which will allow malware to be loaded under the guise of an authentic cryptographic signature.
The loophole could affect 99 per cent of all Android devices and is essentially a security "master key" says Bluebox Security CTO Jeff Foristal. Because the modifications to the APK code do not affect an app's signature, neither handsets, tablets or the various Android marketplaces will be able to distinguish trojan programs from genuine code, meaning that data can be hijacked and hardware 'zombied'.
Forristal says that the issue dates back four years to Android 1.6, or Donut, and thus could affect nearly 900 million operating systems.
"While the risk to the individual and the enterprise is great," writes Forristal, "(a malicious app can access individual data, or gain entry into an enterprise), this risk is compounded when you consider applications developed by the device manufacturers (e.g. HTC, Samsung, Motorola, LG) or third-parties that work in cooperation with the device manufacturer (e.g. Cisco with AnyConnect VPN) - that are granted special elevated privileges within Android - specifically System UID access.
"Installation of a Trojan application from the device manufacturer can grant the application full access to Android system and all applications (and their data) currently installed. The application then not only has the ability to read arbitrary application data on the device (email, SMS messages, documents, etc.), retrieve all stored account & service passwords, it can essentially take over the normal functioning of the phone and control any function thereof (make arbitrary phone calls, send arbitrary SMS messages, turn on the camera, and record calls). Finally, and most unsettling, is the potential for a hacker to take advantage of the always-on, always-connected, and always-moving (therefore hard-to-detect) nature of these 'zombie' mobile devices to create a botnet."
Forristal will be making more details of the discovery public at the 2013 Black Hat security convention, where he's speaking later this year. Forristal says the bug was reported to Google in February, 2013.