Category Archives: Security

aka infosec

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.

Firefox 57: faster and better

I’ve been using Firefox 57 for a few days now, since it was released on November 14. So far, I like what I see. Mozilla is hyping how much faster the browser is, and while it doesn’t feel a lot faster, it is indeed somewhat snappier. Given that Firefox had been getting noticeably sluggish in recent months, this is very welcome.

There are some major changes in Firefox 57: the user interface (UI) has had a major overhaul, using a new set of design guidelines called Photon. Most user interface elements will look familiar, but slightly different. Photon’s main objectives are to improve performance while making the interface consistent across various platforms. You’ll notice new icons throughout (including the main application icon), new positioning of interface elements, new animations, new appearance and behaviour for tabs, cleaned up menus, and new page loading animation.

The ‘new tab’ page has also been improved, and is more customizable. There are some new search engines to choose from, and Google is now the default for search. The on-page search feature now includes an option to highlight all matches on a page.

Numerous other changes in Firefox 57 were made to improve performance, including a new CSS engine called Stylo. CSS stands for Cascading Style Sheets, and it’s a set of standards used by web developers to define the style and layout of web sites. Stylo is faster than its predecessors because it uses available processing power more sensibly.

The upgrade process for Firefox 57 is no different than for earlier versions, and you don’t need to do anything special. As always, your existing Firefox profile (which contains your settings, bookmarks, login credentials, history, etc.) will be used by the new version. You may notice that your toolbar has been rearranged slightly, but that’s easy to fix using the Customize feature. You may also see blank spacer elements on either side of the address box, but these can be removed.

I noticed one possible problem: the contents of the address bar drop-down list occupy a narrow section in the middle of the list. The width of that section matches the width of the address box itself. This may have been done intentionally, but in my opinion it looks weird and severely limits the displayable length of addresses in the list.

With version 57, Firefox is no longer quite as sensitive about the use of Windows accessibility features. Previously, running the Windows On-Screen Keyboard would trigger Firefox to disable multi-process mode, resulting in reduced performance. That no longer happens in Firefox 57.

Firefox 57 also includes fixes for fifteen security vulnerabilities, so even if you’re not sure about the new user interface, you should really go and ahead and upgrade.

All in all, it’s good news for Firefox fans: Firefox 57 is faster, and has a cleaner, tighter, and more consistent user interface. I don’t see any reason to hold off on upgrading.

Firefox 57 may even be good enough to slow the recent wave of users, fed up with Firefox’s increasing bloat and decreasing performance, and feeling abandoned after Mozilla recently orphaned thousands of useful add-ons, who have been switching to Chrome and other browsers.

November updates for Adobe products

Adobe logoYesterday, Adobe announced updates for several of its main products, including Flash, Acrobat Reader, and Shockwave.

Flash 27.0.0.187 addresses five critical vulnerabilities in earlier versions. You can download the new desktop version from the main Flash download page. That page usually offers to install additional software, which you should avoid. Chrome will as usual update itself with the new version, and both Internet Explorer and Edge will get their own updates via Windows Update.

Acrobat Reader 11.0.23 includes fixes for a whopping sixty-two vulnerabilities, all flagged as critical, in earlier versions. Download the full installer from the Acrobat Reader Download Center.

Shockwave Player 12.3.1.201 addresses a single critical security issue in earlier versions. Download the new version from the Adobe Shockwave Player Download Center.

If you use Flash, Reader or Shockwave to view content from untrusted sources, or if you use a web browser with add-ons enabled for any of these technologies, you should update affected systems immediately.

Patch Tuesday for November 2017

According to Microsoft’s announcement, the November updates include patches for Internet Explorer, Edge, Windows, Office, and .NET. As usual, you have to dig into the rather awkward Security Update Guide to find additional details.

My analysis of the SUG reveals that there are fifty-three bulletins, addressing fifty-four vulnerabilities across the usual range of products. Sixteen of the vulnerabilities are flagged Critical.

If you’re interested in performing your own analysis, I strongly suggest avoiding the cumbersome SUG interface. Instead, locate the almost hidden ‘Download’ link at the top right of the updates grid and click that to open the data in Excel. From there you can use Excel’s filtering tools to wrestle the update information into more manageable lists.

KRACK Wi-Fi vulnerability: what you need to know

Last week, security researchers identified a series of vulnerabilities affecting almost all Wi-Fi devices, from computers to refrigerators. The vulnerability could allow attackers to intercept wireless communications and potentially steal credentials and other sensitive information. The vulnerabilities are collectively referred to as KRACK.

The good news is that computers running Windows and Linux already have patches available. Microsoft included fixes in the October 2017 Patch Tuesday updates.

Apple says that fixes are ready for MacOS, but there’s no word on exactly when they will actually be made available.

The bad news is that mobile devices, particularly those that run Google’s Android operating system, are vulnerable, and in some cases, might stay that way indefinitely. That’s because even though Google has prepared fixes for Android, those fixes won’t get to devices made by other vendors until those vendors make them available. Some vendors are better than others at pushing updates to their devices. Worse, some devices running older O/S versions may never get updates at all, rendering them permanently insecure.

There are mitigating factors. First, because of the responsible way in which these vulnerabilities were reported, Microsoft and other major players have had time to develop fixes, while details of the vulnerabilities were kept relatively secret until recently. That means we have a head start on the bad guys this time.

Second, exploiting these vulnerabilities requires close proximity. Attacks based on these vulnerabilities can’t be executed over the Internet.

Use caution with unpatched devices

If you use a public Wi-Fi access point with an unpatched device, you’re exposed. So until patches for your device become available, you might want to disable its Wi-Fi when you’re not at home. Most devices have settings that prevent automatically connecting to Wi-Fi networks it finds in the vicinity.

IoT devices may remain vulnerable forever

‘Internet of Things’ (IoT) devices, including thermostats, cars, appliances, and basically anything that can have a computer stuffed into it, often connect to the Internet using Wi-Fi. There are no security standards for IoT devices yet, and many are extremely unlikely to ever be patched.

Recommendation: identify all of your IoT devices that have the ability to connect to the Internet. For each, make sure that you’re using a wired connection, or disable networking completely, if possible. As for devices that connect to the Internet via Wi-Fi and cannot or won’t be patched or disabled, consider taking them to the nearest landfill.

References