Mobile

12/15/2017
11:02 AM
50%
50%

Mobile Device Makers Increasingly Embrace Bug Bounty Programs

Samsung is the latest to join a small group of smartphone makers to cast their net wide on catching vulnerabilities in their devices.

With the rise of mobile threats and ubiquitous use of smartphones, mobile device makers are increasingly throwing their resources toward bug bounty programs to shore up the security of the devices.

Samsung, which holds the largest market share for Android devices, launched a bug bounty program earlier this year, offering up to $200,000 per vulnerability discovered, depending on its severity. It joined Apple, which launched its bug bounty program in 2016, as well as Google, which kicked off its Android Security Rewards Program in 2015. Silent Circle, which offers Blackphone, was the first mobile company to hold a bug bounty back in 2014.

"Is this a sign that mobile device makers are taking security more seriously? Absolutely," says Alex Rice, co-founder and chief technology officer of HackerOne. "It rises the tide for everyone and the ones that don't do it will look like outliers."

Bug bounties, which reward ethical hackers for finding vulnerabilities in software and hardware, have been around since Netscape kicked off the first one in 1995, but only recently have mobile device makers joined the pack.

Bug bounty programs can be offered and managed by companies that want to find vulnerabilities in their own products, or can be outsourced to a bug bounty company, such as HackerOne or Bugcrowd, to manage. Some bug bounty programs are public, while others are private invite-only affairs.

Catalyst for Change

It has taken mobile device makers awhile to offer bug bounty programs because they have had to wait for the mobile ecosystem to mature, Rice says.

"Mobile device makers are inter-connected with other partners," Rice explains. "They don't have control over the entire attack surface … If you're the manufacturer, you want to only offer a bug bounty program for something you can fix."

But with more partners in the mobile device stack offering bug bounty programs, such as chipset maker Qualcomm and Google's Android, it is easier for mobile device manufacturers to do the same, he says.

"Although only vulnerabilities that are specific to Samsung mobile devices or its apps are eligible for its program, at least now they have a cohesive story to where they can redirect [bug hunters] to other partners in their stack."

Another challenge for mobile bug bounty programs is finding enough researchers to participate in the programs, says Casey Ellis, founder and chief technology officer of Bugcrowd.

Three or four years ago, Bugcrowd had to inform and solicit the ethical hacker community to focus on mobile devices and to get in early on the ground floor, Ellis recalls. But, in some respects, it has been a tough sell.

"Mobile devices are harder targets than web and mobile apps, so in the bounty context, the hacker return on investment can draw folks away from them. That said, it’s an extremely valuable skill set and a rapidly growing attack surface," Ellis notes.

Mobile bug bounty hunters also face a challenge in getting access to all of the components in a device, which adds another layer of complexity and work, Rice says.

Hard Money, Soft Money

A discovery of a hardware vulnerability tends to pay out more than a software flaw in bug bounty programs, say bug bounty experts.

"Finding vulnerabilities in hardware often requires more research, time, and a rarer set of skills than bug finding in applications," Ellis says. "Because of this, hardware bugs are typically priced higher to reflect their impact and to incentivize talented researchers to join the hunt."

Rice noted vulnerabilities that allow remote code execution in trust environments also tend to yield the largest bounty payments.

Although Samsung, Google, and Apple all offer bounty rewards upwards of $200,000, depending on the severity of the vulnerabilities discovered, a HackerOne report notes the average payout for mobile critical vulnerabilities ranges from $383 per bug for the telecom industry to $2,015 for the technology industry.

"I expect to see the amount of bounties rise," Rice says. "I predict we'll see more players in the future and more coverage with the bounty programs for mobile devices and apps."

Related Content:

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.