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.

Vulnerabilities / Threats

2/14/2018
04:35 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Intel Expands Bug Bounty Program, Offers up to $250K

Microprocessor giant adds vulnerability-finding category for Meltdown, Spectre-type flaws.

Intel is doubling down on its existing bug bounty program by opening it up to all security researchers and adding an entire category for vulnerabilities akin to the dangerous Meltdown and Spectre flaws recently exposed in its microprocessors.

The chip company today announced that it had expanded its nearly one-year old bug bounty program in an effort to forge closer ties to the security research community and offer bigger financial incentives for coordinated response and disclosure of flaws in its products.

Intel previously ran an invitation-only bug bounty program. In addition to opening up its vulnerability compensation program to all researchers, Intel also added a section specifically for side-channel vulnerabilities through Dec. 31 of this year. Researchers who discover these types of bugs can earn up to $250,000, the company said.

"In support of our recent security-first pledge, we’ve made several updates to our program. We believe these changes will enable us to more broadly engage the security research community, and provide better incentives for coordinated response and disclosure that help protect our customers and their data," Rick Echevarria, vice president and general manager of platform security at Intel wrote in a post announcing the changes.

Intel also raised bug bounty award amounts overall, with grants up to $100,000. The company's program runs on HackerOne's platform

These changes to the program come in the wake of the major disclosure last month of critical flaws in most modern microprocessors, including Intel's: a common method used for performance optimization could allow an attacker to read sensitive system memory, which could contain passwords, encryption keys, and emails, for example.

The so-called Meltdown and Spectre hardware vulnerabilities allow for so-called side-channel attacks. With Meltdown, sensitive information in the kernel memory is at risk of being accessed nefariously; with Spectre, a user application could read the kernel memory as well as that of another application. The end result: an attacker could read sensitive system memory containing passwords, encryption keys, and emails — and use that information to help craft a local attack.

Intel's new bug bounty program for side-channel vulns focuses on vulnerabilities in hardware that are exploitable in software, the company said. "Through this special program, Intel hopes to accelerate new innovative research and learning around these types of security issues," Intel said in a post detailing the short-term bounty.

The bug bounties for the side-channel flaws range from up to $5,000 for low-severity flaws to $250,000 for critical flaws.

"Like many large, complex organizations, Intel is searching for the right incentive model to help protect their users and supply chain partners. It isn't as simple as throwing more money at a problem to really secure the Intel ecosystem," says Katie Moussouris, founder of Luta Security. "Careful reward structures that are lawful for the company, the participating hackers, the partners, and the customers take a considerable amount more to develop, so I hope for all of society's sake that chip manufacturers and other members of the global critical computing infrastructure evolve thoughtfully to bounty smarter, not harder."

Intel has been under fire for the fallout experienced by the initial firmware fixes it released for Meltdown and Spectre. The company issued an unusual advisory late last month  urging its customers and partners to refrain from applying some of the firmware patches. Navin Shenoy, executive vice president and general manager of Intel's Data Center, called for customers and OEMs to halt installation of patches for its Broadwell and Haswell microprocessors after widespread reports of spontaneous rebooting of systems affixed with the new patches.

Meanwhile, Intel CEO Brian Krzanich told analysts in an earnings call late last month that the company will roll out new products later this year that mitigate the Meltdown and Spectre vulnerabilities.

Alex Rice, co-founder and CTO of HackerOne, says Intel's short-term bounty for side-channel vulnerabilities makes sense. "Bounty programs are more powerful the more they incentivize the specific type of research that would be most valuable to the company," he says. "In Intel's case, side-channel attacks are a highly complex specialization that their team has invested heavily in defending against."

Related Content:

 

 

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. 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 ... View Full Bio
 

Recommended Reading:

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
Navigating the Asia-Pacific Threat Landscape: Experts Dive In
Kelly Sheridan, Staff Editor, Dark Reading,  9/25/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-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> ...