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.

Security Management //

Patch Management

08:05 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now

Intel Boosts Bug Bounties in Wake of Spectre & Meltdown

Intel is increasing its bug bounty program in the wake of the controversy surrounding the Spectre and Meltdown vulnerabilities found within the company's x86 CPUs.

Intel created its first bug bounty program in March with the purpose of engaging the security community and incentivizing researchers to find vulnerabilities in the company's chips.

Now, in the wake of Spectre and Meltdown, the program is expanding.

The expanded Intel Corp. (Nasdaq: INTC) Bug Bounty Program, which the chip maker announced February 14, highlights three specific improvements to help deal with issues such as Spectre and Meltdown, as well as Intel's pledge to be more open to security concerns. (See Security Warning: Intel Inside.)

Specifically, the bug bounty program update focuses on side-channel vulnerabilities, which are akin to Spectre and Meltdown, which came to light earlier this year, following the release research paper that has dinged Intel's reputation in the security community. (See Intel CEO Promises Chips That Fix Spectre & Meltdown Flaws .)

(Source: Intel)
(Source: Intel)

These updates include:

  • A shift away for an invitation-only program to one that is open to all security researchers, which should increase the pool of those looking for flaws and vulnerabilities in the company's CPUs.
  • Between now and December 31, Intel will offer rewards of up to $250,000 for information on side-channel vulnerabilities.
  • An overall increase in the amount of money the company pays in bug bounties, including as much as $100,000 for details about certain vulnerabilities and flaws.

"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 of Software and Services Group and the general manager of Platforms Security Division, wrote in Wednesday's blog post.

The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

The specific requirements about how to apply to the bug bounty program and what it takes to collect the bounties can be found on Intel's security site.

When news about Spectre and Meltdown broke in January, Intel issued several patches to fix the problem, but those were criticized as slowing down CPU performance, as well as other problems. ZDNet recently reported on a test that showed issues with the Meltdown patch. (See Linus Torvalds: Intel's Spectre Patch Is 'Complete & Utter Garbage'.)

Other companies have looked to offer different tools to help mitigate the problems with Spectre and Meltdown. This week, Microsoft Corp. (Nasdaq: MSFT) offered a free update to its Windows Analytics service that allows IT departments to track Spectre and Meltdown updates and issues throughout a PC fleet.

In addition, Microsoft released a security update on Tuesday to fix issues in Outlook, Internet Explorer, Windows, Office, Edge and other products. Redmond also updated the frequently asked questions section of its Security TechCenter site to address issues related to side-channel vulnerabilities.

Related posts:

— Scott Ferguson, Editor, Enterprise Cloud News. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-10-26
Cross-site scripting vulnerability in Movable Type Movable Type Premium 1.37 and earlier and Movable Type Premium Advanced 1.37 and earlier allows a remote authenticated attacker to inject an arbitrary script via unspecified vectors.
PUBLISHED: 2021-10-26
An issue was discovered in Nagios XI 5.8.5. Insecure file permissions on the nagios_unbundler.py file allow the nagios user to elevate their privileges to the root user.
PUBLISHED: 2021-10-26
An issue was discovered in Nagios XI 5.8.5. In the Custom Includes section of the Admin panel, an administrator can upload files with arbitrary extensions as long as the MIME type corresponds to an image. Therefore it is possible to upload a crafted PHP script to achieve remote command execution.
PUBLISHED: 2021-10-26
An issue was discovered in Nagios XI 5.8.5. In the Manage Dashlets section of the Admin panel, an administrator can upload ZIP files. A command injection (within the name of the first file in the archive) allows an attacker to execute system commands.
PUBLISHED: 2021-10-26
An issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (ty...