Endpoint

1/9/2018
12:10 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Microsoft Confirms Windows Performance Hits with Meltdown, Spectre Patches

Windows servers will see biggest degradation, as will Windows 7 and 8 client machines, Microsoft said.

It's official: Microsoft Windows patches for recently revealed critical microprocessor flaws will cause noticeable performance slowdowns on Windows machines, the company said today.

Performance degradation has been a key concern after Microsoft and Linux operating system kernels were retooled to mitigate attacks on Intel, AMD, and ARM processors via the so-called Meltdown and Spectre hardware vulnerabilities. Security experts had estimated up to 30% degradation for Linux and Windows, so performance is a big part of the equation when it comes to risk assessment and in some cases, whether to patch at all.

Microsoft in a blog post today confirmed that Windows servers will experience noticeable performance slowdowns, as will Windows 7 and 8 client machines running older processors (2015-timeframe PCs with Haswell or older CPUs). While newer Windows 10 platforms won't experience perceptible performance drops, those on older hardware will.

What's What

To be fully secured from the flaws, machines must apply the operating system, browser, and microcode patches, says Frank Shaw, communications lead at Microsoft, in a Dark Reading interview.

Specifically, Windows 10 client machines running modern microprocessors (2016-era PCs with Skylake, Kabylake, or newer CPUs) will suffer some performance hits, but it won't be "user-perceptible," according to Microsoft. "It will be a couple of percentage points, depending on various workloads. It's not something people will truly notice,” says Shaw.

Windows 10 machines on Haswell-class or older microprocessors however will experience noticeable performance changes in some cases, however, Shaw says.

And older Windows 7 and Windows 8 machines will experience performance degradation with the patches. "For context, on newer CPUs such as on Skylake and beyond, Intel has refined the instructions used to disable branch speculation to be more specific to indirect branches, reducing the overall performance penalty of the Spectre mitigation," Microsoft said. "Older versions of Windows have a larger performance impact because Windows 7 and Windows 8 have more user-kernel transitions because of legacy design decisions, such as all font rendering taking place in the kernel. We will publish data on benchmark performance in the weeks ahead."

Microsoft said it's working on fine-tuning the Windows performance of its patches. This is especially crucial for Windows servers.

"Windows Server on any silicon, especially in any IO-intensive application, shows a more significant performance impact when you enable the mitigations to isolate untrusted code within a Windows Server instance. This is why you want to be careful to evaluate the risk of untrusted code for each Windows Server instance, and balance the security versus performance tradeoff for your environment," according to Microsoft.

Windows Fixes

In its Windows update for the one variant of the Spectre Bounds Check Bypass attack (CVE-2017-5753), Microsoft made a compiler change and hardened its Edge and IE 11 browsers to prevent JavaScript-borne exploits, a fix that doesn't require processor a microcode update on the machine.

For the Spectre Branch Target Injection (CVE-2017-5715), Microsoft's patch alerts Windows to call new CPU instructions in the case of risky scenarios with the side-channel communications process. That patch requires the microprocessor update on the machine.

For Meltdown's so-called Rogue Data Cache attack (CVE-2017-5754), Microsoft said it isolated kernel and user-mode page tables to thwart such an attack; no microcode updates are needed on the machine for that fix.

"Because Windows clients interact with untrusted code in many ways, including browsing webpages with advertisements and downloading apps, our recommendation is to protect all systems with Windows Updates and silicon microcode updates," Microsoft said in its post.

Meanwhile, Microsoft recommends that server administrators employ mitigations at the physical layer of the server to isolate virtualized workloads on the server. Azure was already updated accordingly to protect virtual machine environments, according to the company. "For on-premises servers, this can be done by applying the appropriate microcode update to the physical server, and if you are running using Hyper-V updating it using our recent Windows Update release."

There are additional mitigation options for Windows Server as well within VMs to vet untrusted code, for example.

When is okay not to patch? If a system is not running "untrusted" applications, Microsoft's Shaw says. "IT pros in some cases will not deploy microcode [patches if they] have an environment where they don't need to worry about it: if they are not running untrusted applications," he says.

"This is a hardware problem that affects chips, operating systems," he says. "We wanted to let customers know what to expect" with performance, he says. "You won't notice if it's a spinning disk, but if it's a solid-state disk, you will notice" performance hits, Shaw says.

The good news: there are no exploits in the wild right now, he says. Consumers and businesses should install Windows and Apple OS updates, and "then when microcode is available from OEMs," it should also be installed, he says.

"On the client side, we would certainly hope customers will deploy the full solution" for patches, he says. "On the server side, IT pros can look at their specific use cases and make a decision."

Microsoft has patched 41 of its 45 editions of Windows, and expects to have the remaining four issued "soon," the company said in its post.

The company has further information on microcode updates from OEMs here, and information on specific system patches here:

 

Related Content:

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Ericka Chickowski, Contributing Writer, Dark Reading,  5/15/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Typin' in my password. Somebody's shoulder surfin'. Woooh!
Current Issue
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11329
PUBLISHED: 2018-05-22
The DrugDealer function of a smart contract implementation for Ether Cartel, an Ethereum game, allows attackers to take over the contract's ownership, aka ceoAnyone. After that, all the digital assets (including Ether balance and tokens) might be manipulated by the attackers, as exploited in the wil...
CVE-2018-11363
PUBLISHED: 2018-05-22
jpeg_size in pdfgen.c in PDFGen before 2018-04-09 has a heap-based buffer over-read.
CVE-2018-11364
PUBLISHED: 2018-05-22
sav_parse_machine_integer_info_record in spss/readstat_sav_read.c in libreadstat.a in ReadStat 0.1.1 has a memory leak related to an iconv_open call.
CVE-2018-11365
PUBLISHED: 2018-05-22
sas/readstat_sas7bcat_read.c in libreadstat.a in ReadStat 0.1.1 has an infinite loop.
CVE-2018-11339
PUBLISHED: 2018-05-22
An XSS issue was discovered in Frappe ERPNext v11.x.x-develop b1036e5 via a comment.