Vulnerabilities / Threats
11/5/2013
04:41 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Custom Features Incur Security Flaws In Popular Android Smartphones

Researchers find vulnerabilities in preloaded customized apps and features

It's not the Android app stores that you need to worry most about: The biggest security weaknesses in most Android smartphones today are the custom apps and features that come packaged with the devices, new research shows.

Those are some of the findings from researchers at NC State who recently studied how custom vendor features on Android smartphones affect the security of the devices. Some 60 percent of all vulnerabilities the researchers found in popular smartphone models were due to what the researchers call "vendor customizations," or features the smartphone manufacturers tweak or include with the phones.

Another shocker: Newer smartphone models aren't necessarily more secure, according to NC State researchers Lei Wu, Michael Grace, Yajin Zhou, Chiachih Wu, and Xuxian Jiang, who will present their research tomorrow at the ACM Conference on Computer and Communications Security in Berlin.

"We all know that Android, though popular, has one major problem: fragmentation. Among other [things], vendor customizations play a key role in contributing to the fragmentation," Jiang said in an email interview. "We are interested in better understanding how vendor customizations will impact overall Android security."

[Google Android's single sign-on feature 'weblogin' convenient but risky to an organization's Google Apps, DEF CON researcher shows. See One Hacked Android User Can Lead To An Enterprise Breach .]

Jiang and his team studied Android Version 2.X and Version 4.X models from Samsung, HTC, LG, Sony, and Google -- specifically, the Samsung Galaxy S2 and S3; the HTC Wildfire S and One X; the LG Optimus P350 and Optimus P880; Sony Xperia Arc S and Xperia SL; and the Google Nexus S and Nexus 4. Some 80 percent of the apps on those phones were preloaded and customized by the smartphone manufacturers; all 10 devices were vulnerable due to those preloaded apps.

Jiang said the team's research uncovered other surprising trends: On average, 85 percent of all of these preloaded apps have too many user privileges on the devices, thanks to vendor customization. That means an app gets permissions it wouldn't actually use, such as the ability to send SMS messages, record audio, or make phone calls without the user's permission, for example.

The Android Version 2.x phones each contained an average of 22.4 vulnerabilities; the newer Version 4.x phones, an average of 18.4 vulnerabilities.

Upgrading to the newest smartphone model doesn't necessarily help securitywise, the researchers found. Every time the vendor customizes more features on the phone, it opens the door for more security flaws. "While a newer Android phone may run a newer version of OS , which might already fix vulnerabilities present in older versions, vendor customizations, however, being significant on these devices, could still introduce additional vulnerabilities into newer phones," Jiang said.

Of the Android 4.x phones, the Google Nexus 4 performed the best, with just three total vulnerabilities, and the Galaxy S3 fared worst, with 40 total bugs. That was only a slight improvement overall from the Android 3.x phones, however, where the Google Nexus S and the Sony Xperia Arc each had eight flaws (the lowest), the HTC Wildfire S had 40 flaws, and the Samsung Galaxy S2, 39.

Buyers can't do much about these preloaded apps, Jiang said, but smartphone manufacturers can step up by taking security and privacy more seriously in their designs. He said they should adopt the least-privilege principle when building apps and conduct white- and black-box vulnerability analysis to find and fix bugs.

"Through this study, we hope to highlight the need for heightened focus on security by the smartphone industry. And the work was supported in part by the U.S. National Science Foundation," Jiang says.

The full NC State research paper, titled "The Impact of Vendor Customizations on Android Security," is available here (PDF) for download.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is Senior Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise Magazine, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3541
Published: 2014-07-29
The Repositories component in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to conduct PHP object injection attacks and execute arbitrary code via serialized data associated with an add-on.

CVE-2014-3542
Published: 2014-07-29
mod/lti/service.php in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) is...

Best of the Web
Dark Reading Radio