Major slowdowns headed for almost all computers

Major patches are coming, for most operating systems and devices running modern (made in the last 10 years or so) processors. Changes to Windows, Linux, macOS, and most other systems will modify the way memory is used, ameliorating critical CPU security flaws, and slowing them down significantly in the process.

There’s been a lot of secrecy around this issue, with details of the flaws — discovered several months ago — only now coming to light as O/S vendors scramble to prepare patches. The flaws (commonly referred to as Spectre and Meltdown) involve potential leaking of information, as described in a recent post on The Register:

At best, the vulnerability could be leveraged by malware and hackers to more easily exploit other security bugs.

At worst, the hole could be abused by programs and logged-in users to read the contents of the kernel’s memory. Suffice to say, this is not great. The kernel’s memory space is hidden from user processes and programs because it may contain all sorts of secrets, such as passwords, login keys, files cached from disk, and so on.

Much of this is still speculation, but the reality may be even worse, so hang onto your socks, since this is going to get ugly. It’s easy to imagine class action lawsuits arising out of the mess.

Those of you running light operating systems on older hardware may have the last laugh: while many of the world’s computers will soon be noticeably — and unavoidably — slower, yours will keep chugging along unaffected… at least until they’re used to access any of the millions of computers that power web sites and services. Major providers may have no choice but to install the updates, significantly reducing the processing power of their systems.

For computers running Windows 10, system updates are literally unavoidable, and the slowdown inevitable. The rest of us will need to decide whether to risk leaving the vulnerabilities exposed, or patch them and deal with the resulting performance hit. Exploiting the vulnerabilities is not straightforward, and it should be possible to stay safe by avoiding risky behaviour, such as indiscriminately running unknown software, visiting dubious web sites, and opening links in email. However, the full extent of the risks involved is not yet known.

Related articles

The Verge: Intel’s processors have a security bug and the fix could slow down PCs
The Verge: Microsoft issues emergency Windows update for processor security bugs
The Verge: Intel says processor bug isn’t unique to its chips and performance issues are ‘workload-dependent’
The Verge: Processor flaw exposes 20 years of devices to new attack
The Verge: How to protect your PC against the major ‘Meltdown’ CPU security flaw
Google Security Blog: Today’s CPU vulnerability: what you need to know
Bruce Schneier: Spectre and Meltdown Attacks
SANS InfoSec: Spectre and Meltdown: What You Need to Know Right Now
Techdirt: A Major Security Vulnerability Has Plagued ‘Nearly All’ Intel CPUs For Years

Update 2018Jan04: Corrected title and content to show that the problem affects all modern processors, not just those made by Intel, and that there are multiple vulnerabilities. Also added more related articles.

Vivaldi 1.13.1008.40

The latest version of Vivaldi includes some security fixes from a newer version of the Chromium browser engine, so this is an important update.

Other changes in Vivaldi 1.13.1008.40 are almost all regressions, meaning that they are fixes for things that were previously fixed but broke again in recent updates. The frequency of these regression issues in Vivaldi is troubling, as it seems to indicate some sloppiness in the development process.

The announcement for Vivaldi 1.13.1008.40 makes no mention of the new version number, and fails to link to anything like a change log. It’s unclear whether these omissions were intentional, or just mistakes.

Chrome 63.0.3239.108

Two security vulnerabilities, one of which has a High risk rating, are addressed in Chrome 63.0.3239.108. The log lists a few additional changes, none of which are particularly interesting.

There’s no easy way to disable automatic updates in Chrome. Generally, if there’s an update available, it will find its way to your computer within a few days via Google’s Update Service.

You can usually trigger an update by navigating to the About Chrome page ( > Help > About Google Chrome).

Opera 49.0.2725.56

Opera just updated itself on my main computer, and now I’m running version 49.0.2725.47, which Opera itself says is the latest version. Which is odd, because the change log for Opera 49 shows the most recent set of changes is for version 49.0.2725.56.

Version confusion aside, the changes listed for Opera 49.0.2725.56 appear to be minor bug fixes. Which is weird, because the new version announcement mainly talks about improvements to Opera’s built-in VPN (Virtual Private Network) feature. The updated VPN service is apparently faster and better; it’s also now hosted on Opera’s own servers instead of SurfEasy’s.

If you use Opera’s built-in VPN, version 49.0.2725.56 may be worth exploring. Otherwise it’s unlikely to be of much interest.

Vivaldi 1.13.1008.36

Vivaldi’s new version announcements seem to be getting worse. Version 1.13.1008.36 was released a few days ago as another ‘Minor update to Vivaldi 1.13’, but details are scant: the new version number is never actually mentioned, and there’s no reference to any release notes.

The announcement does at least provide a brief list of the new version’s changes, which consist of a few bug fixes and an update to the Chromium engine that includes security fixes.

Given that there are security fixes in this release, Vivaldi users should probably upgrade as soon as possible. You can do that by clicking the browser’s ‘V’ menu at the top left, then Help > Check for Updates.

Mirai botnet update

It wasn’t Russia, or China, or any other nation-state. The motive wasn’t political. The IoT-based Mirai botnet was created by three young American men as a tool for crippling Minecraft servers and related services.

Of course, once Mirai’s authors realized the unprecedented power of their creation, they started using it for other things: as a tool for gaining customers for an anti-DDoS service; to kick Brian Krebs’ web site off the Internet as revenge for outing the authors of vDOS; and later as a lucrative click fraud engine.

Last week, in a courtroom in Alaska, Mirai’s creators all pleaded guilty to charges related to Mirai, including conspiracy to violate the Computer Fraud and Abuse Act (CFAA). FBI agents had tracked the botnet’s activities to the trio.

While I’m happy that these assholes have been caught, and are likely to spend significant time behind bars, Mirai is a sobering reminder of the fragility of the Internet. The earliest version of the Internet was ARPANET, which was literally designed to withstand nuclear attack. But even nukes can’t compare with the power of smart, young people with plenty of spare time. Not long after the Internet was born, a college student named Robert Morris brought the nascent network to its knees with a simple software worm.

Meanwhile, because the Mirai authors shared the botnet’s source code (in a futile attempt to confuse investigators), Mirai clones are popping up regularly, and doing a lot of damage.

Still, it’s encouraging to see that the FBI and other agencies are getting better at tracking the perpetrators of these malicious schemes. Other recent arrests include the person behind an attack on Deutsche Telekom that used a Mirai variant; and the operator of the Kelihos botnet. Hopefully these arrests will provide a sufficient deterrent for those similarly inclined.

Flash 28.0.0.126

Adobe logoAdobe released a new version of Flash to coincide with yesterday’s Microsoft updates. Flash 28.0.0.126 fixes a few minor issues and one security vulnerability.

As usual, Chrome will update itself with the latest Flash, and Microsoft browsers will receive updates via Windows Update.

If you still use Flash, and in particular if you use a web browser that is configured to play Flash content, you should install the new version as soon as possible. Better still, stop using Flash altogether. Flash is being phased out in some browsers, including Firefox. Many web sites that formerly used Flash have switched to HTML5.

Patch Tuesday for December

Today, Microsoft published twenty-four updates, addressing thirty-three vulnerabilities in Flash player (for Microsoft browsers), Office, Internet Explorer, Edge, and Windows.

As usual, Microsoft’s announcement is little more than a pointer to the Security Update Guide (SUG). If you’re looking for details about any of these updates, that’s your only official option. The SUG’s user interface is somewhat headache-inducing, but there’s useful information to be had there.

Windows 10 gets these updates whether you want them or not; Windows 7 and 8.1 can be configured for automatic or manual updates. I personally don’t like the idea of updates being installed on my computers at Microsoft’s whim, so I’m sticking with manual updates. And avoiding Windows 10 completely. And gradually switching to Linux.

Firefox 57.0.2

According to the release notes, Firefox 57.0.2 fixes two bugs, neither of which is related to security. And yet there’s also a security advisory for Firefox 57.0.2, which lists two vulnerabilities fixed in the new version.

In the past, Mozilla linked to relevant security advisories on Firefox release notes pages, so presumably someone simply forgot. Fixes for security bugs are a lot more important than fixes for obscure non-security-related bugs, so hopefully this isn’t the new normal for Firefox release notes.

Since this update includes security fixes, it’s a good idea to make sure your Firefox installation is up to date. You can do that by clicking its menu button at the top right (three horizontal lines, sometimes referred to as a ‘hamburger’ button), then choosing Help > About.

Chrome 63.0.3239.84

The change log for Chrome 63.0.3239.84 has ten thousand entries. I’d like to read it, and I might even find something interesting buried there, but instead I’ll assume Google would point out any notable changes in the release notes.

Alas, while the release notes do point out that the new Chrome includes fixes for thirty-seven security vulnerabilities, none of the other changes are discussed. In a way I suppose that’s a good thing: as long as Google isn’t making large changes or adding new features, while they continue to fix vulnerabilities and other bugs, the outcome is almost always going to be a better browser.

Chrome typically updates itself within a few hours or days of a new release, although in the release notes, Google says “This will roll out over the coming days/weeks.” Given the number of security fixes in this version, it’s a good idea to check the version you’re running, and hopefully trigger an update, by clicking Chrome’s menu button (three vertical dots at the top right), then choosing Help > About Google Chrome.

Rants and musings on topics of interest. Sometimes about Windows, Linux, security and cool software.