Vulnerabilities / Threats

11/4/2015
05:20 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

AndroBugs: A Framework For Android Vulnerability Scanning

At Black Hat Europe next week, a researcher will present a framework he says is more systematic than the vulnerability scanners popping up on the market.

The Android ecosystem is a Wild West where vulnerabilities can run rampant, and go undiscovered, unchecked, and unfixed. It's hard to corral, but a researcher at Black Hat Europe in Amsterdam next week will present a new framework to help make the process of locating vulnerabilities in Android apps and libraries more efficient and more accurate.

Yu-Cheng Lin, software engineer on the security team at MediaTek, will introduce the “AndroBugs Framework: An Android Application Security Vulnerability Scanner.”

"I found that the same mistakes are being made again and again by Android developers," Lin says. "So I believe probably I can find many security vulnerabilities if I use a systematic way. And actually, the results (vulnerabilities found) from AndroBugs Framework exceeded my expectation."

There are other tools that help Android developers write clean code. Google's Android integrated development environment includes a tool called Lint -- but mostly it finds coding errors, not security weaknesses. There are also some Android vulnerability scanners hitting the market.

Lin says his framework is different.

Instead of just scanning the code for weak spots, AndroBugs tries to emulate the operation of an app, and considers the attack vectors through which those weaknesses would be exploited.

"I think the biggest difference from those tools is the ways that AndroBugs Framework plays with the vulnerability vectors," says Lin.  "... The analysis report from AndroBugs Framework is prioritize, which means it tries not to print the useless information."

Also, AndroBugs stores all its analyses in the NoSQL database and includes tools for users to query the NoSQL database by vector. That can reduce the effort for developers and security pros looking for vulns.

"So if I want to find vulnerabilities among lots of applications (e.g. more than 100,000 apps)," he says. "I will do the massive scanning with AndroBugs Framework first. ... It truly helps you reduce the efforts of finding vulnerabilities and you no longer need to review the code line by line."

When AndroBugs analyzes an app, it scans for vulnerabilities in the third-party libraries/SDKs it uses, too. 

"If a vulnerability is found in a SDK, it’s a disaster," says Lin. "First, it may be used by many applications. Second, unlike system upgrade, the Android developers may not upgrade the libraries they are using."

The good news is that it's actually easier for the AndroBugs Framework to find SDK vulns than others. "If those vulnerable libraries are used by many applications, you actually can find those vulnerable libraries with AndroBugs Framework immediately because lots of applications will use them," Lin says. "So I think the vulnerabilities in SDKs will get fixed faster."

They may be fixed faster, he notes, but that doesn't mean that the Android developers will update and upgrade appropriately, so security problems can still perpetuate themselves within the Android environment -- something Lin doubts will ever change. 

"I think Google will never make [app security] an enforcement or rate the security of an app," he says. "I think Google will never take down the vulnerable apps from Google Play. It’s a political problem. I think Google already knows some security problems in Android applications. But there are too many applications that use the vulnerable APIs."

This is why Lin -- who has also been an Android developer -- uses an iPhone.

Lin says that he hopes AndroBugs will help improve Android security, but he also suggests that companies give mobile security the same attention they give Web security; that Android security researchers exercise responsible disclosure; and that companies acknowledge, not ignore, the vulnerability reports they receive.

The AndroBugs Framework will be released, open-source, on GitHub before Black Hat Europe. A Windows version is also forthcoming.

Black Hat Europe returns to the beautiful city of Amsterdam, Netherlands November 12 & 13, 2015. Click here for more information and to register.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Major International Airport System Access Sold for $10 on Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  7/11/2018
Mueller Probe Yields Hacking Indictments for 12 Russian Military Officers
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/13/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Cyberspace is much less secure than my old lamp.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14363
PUBLISHED: 2018-07-17
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.
CVE-2018-14349
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a NO response without a message.
CVE-2018-14350
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field.
CVE-2018-14351
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size.
CVE-2018-14352
PUBLISHED: 2018-07-17
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap_quote_string in imap/util.c does not leave room for quote characters, leading to a stack-based buffer overflow.