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.

Mobile Security //

Apps

4/4/2019
09:20 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Increased Permissions in Mobile Apps Increases Potential Risk

App user permissions should be justified, but many of them aren't.

Mobile security provider Wandera wondered what the iOS apps it covered in its networks were doing when they requested permissions from a user. So, they looked at 30,000 unique apps that were the most commonly installed within their network of corporate devices in order to find out more about exactly what they were requesting from the user.

This kind of review is novel. While most users will have anecdotal data, a look at how apps as a whole request information has not been previously released.

In the blog that summarizes what they found out, they note that "When it comes to personal information on iPhones, apps are required to request your permission to access it and explain why they need it. Personal information in this context includes things like current location, calendars, contact information, photos and more. Apps usually ask for this level of access to improve functionality but sometimes it's without any justification at all. This becomes an issue when sloppy development leads to bugs that leak data putting your privacy and security at risk. This is why it's best to limit when apps collect this data."

Wandera found that the most requested permissions had to do with photos and locations. Their survey showed "Photo Library" was requested by 62% of apps, "Camera" was requested by 55% of the apps, and "Location When In Use" is requested by 51% of the apps. This kind of request is not surprising, when the uses are considered. Taking pictures of a whiteboard in meetings is not uncommon but it can allow sensitive corporate information to exist in photo libraries.

One-time uses like a profile set-up may also happen. The problem is after that use, the permission may not be rescinded, leaving that access open at all times.

Michael Covington, VP of product strategy at Wandera, spoke with Security Now and said, "Justification to access my personal information should not be a one-time event. As a consumer, I want to know how that PII is transmitted, where it is stored and who has access to it. None of this transparency exists today with mobile apps."

Permissions that are not usually thought of as "high risk" (which means Location Always, Microphone, Photo Library, and Contacts) can be misused and therefore deserve careful review.

While 17% of iOS apps ask for no permissions at all, most apps will request five or fewer permissions.

While Social Network category apps ask for the most permissions (4.96 on average), Weather is close behind (4.73). /p>

Shopping (4.5), Health & Fitness (4.48), and Finance (4.37) apps also ask for many permissions.

Covington realizes the problem goes beyond iOS. He also said that, "We did a study into Android app permissions last year and found similar trends. What's alarming on Android is that apps have more visibility across the device; for example, Android apps can see a list of other apps installed on the device, can read and write with more freedom and can even access more unique identifiers that allow them to pinpoint specific users."

Summing up, Covington has some techniques for users. "In addition to checking permissions, I encourage people to disable the permissions they're not comfortable granting; on iOS, there's a good chance you'll not break the app completely and can still enjoy the benefits it provides, without parting with too much sensitive information. […] I also disable location information for 90% of the applications installed on my device; it's easy enough for me to request the weather at the city-level, rather than share my precise location with the developer throughout the day."/p>

It's always a good idea to review any granted permissions to make sure they are still relevant.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...