Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk //

Compliance

7/18/2013
01:21 AM
50%
50%

Researchers To Highlight Weaknesses In Secure Mobile Data Stores

At Black Hat USA, a team of mobile-security researchers plans to show off ways to circumvent the security of encrypted containers meant to protect data on mobile devices

With employees increasingly working from their personal devices, companies are searching for ways to protect sensitive data from whatever might be inhabiting those untrusted mobile environments.

Click here for more of Dark Reading's Black Hat articles.

One method, frequently referred to as a secure container, uses an encrypted data store to protect the business information on the device from malware or an unauthorized user. Yet such precautions are not enough, says Michael Shaulov, CEO of Israeli startup Lacoon Mobile Security, which will show off ways to circumvent the protection of secure containers this month at Black Hat USA in Las Vegas.

Any malware or user who has access to the operating system will be able to undermine the integrity of the encryption used for most, if not all, secure containers included as part of a mobile device management (MDM) solution, Shaulov says.

"We basically show that once the operating system is compromised, then -- from that point on -- it is trivial for some sort of spyphone [software] to break into the secure container and steal information from there," he says.

The presentation will likely highlight that the bring-your-own-device (BYOD) trend is both a boon and a curse for companies. While employees are more productive and happy on devices that they have bought and own themselves, providing security for business data in such a setting is extremely difficult. The problem for companies is that locking down a worker's phone to the same degree as a company-owned device requires placing intrusive security on the system and allowing the company's IT department to manage the device, Shaulov says.

"You can completely lock down the mobile device, but then it is not BYOD anymore, and no employee will ... stand for that," he says.

Lacoon's presentation will not focus on specific exploits, but a chain of weaknesses that undermine the security of the encrypted containers on devices, Shaulov says. While such techniques have been used to steal data from desktop and laptop computers, mobile devices have mostly not been targeted, he says.

[Two apps currently available for download in Google Play abuse the critical master key vulnerability that affects almost all Android devices. Is Google reviewing apps for the flaw? See Google Play Has Apps Abusing Master Key Vulnerability.]

The researchers' claims are quite feasible, says Troy Vennon, director of Juniper Network's Mobile Threats Center. Having some sort of malware already on the device gives the attacker a leg up in attacking any software running on the machine, he says.

In addition, more malicious software is targeting the Android platform than any other mobile operating system. Because of its market share and open code, Android phones have become the focus of many malware authors, with more than 275,000 malicious apps written for the platform to date, according to Juniper's quarterly mobile threat report released in June. In addition, attackers are increasingly using spyware on mobile devices to gather information about the user -- information that could be sold or used to target the user with social engineering attacks, he says.

And once such software is on the device, gaining access to encrypted data stores is not a great leap, Vennon says.

"Is it viable at this point that malware, if it got system-level access, could bypass the encryption around a secure container?" he says. "It's absolutely possible."

With employee-owned devices, companies should assume that any smartphone or tablet brought in by a worker is compromised, says Kurt Stammberger, vice president of marketing for app-security firm Mocana. "The fact of BYOD is that all your employees are coming with God-knows-what on the device," he says. "Pretty much there is nothing you can do to clean it up."

Mocana, Good Technology, Appthority, and other companies use application wrapping to add security and better manage the applications that handle sensitive business data.

Yet beefing up that security with other layers of protection should be considered, Juniper's Vennon says. While any single technology can be bypassed, by using defense-in-depth methods -- including host-based protection, such as antivirus, mobile-device management, and encrypted communications -- businesses can better protect against the latest attacks, he says.

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. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
WannaCry Has IoT in Its Crosshairs
Ed Koehler, Distinguished Principal Security Engineer, Office of CTO, at Extreme Network,  9/25/2020
Safeguarding Schools Against RDP-Based Ransomware
James Lui, Ericom Group CTO, Americas,  9/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...