Updates for MAC including recent Zero Day – Are you caught up?

updates for macOS Sierra

It’s December; let’s not forget about the MAC community and the recent updates available for the MAC OS.

Since the release of macOS Sierra 10.12.1, Security Update 2016-002 El Capitan, and Security Update 2016-006 Yosemite on the 24th of October 2016, there have been a number of updates to both Apple and 3rd-party products.

Here are some highlights to consider and possible updates you may want to verify you have.

November 30th – Zero Day Critical update CVE-2016-9079 for a use-after-free vulnerability in SVG Animation in Mozilla Firefox, Firefox ESR, and Thunderbird allowing attackers to execute arbitrary malicious code on a target machine.

Although there have only been documented active exploits on computers running Windows, the vulnerability is present in the Mac OS X version of the browser.

November 29th – Update CVE-2016-4780 for a null pointer de-reference issue in macOS Sierra 10.12 Thunderbolt allowing applications to execute arbitrary code with kernel privileges. This update includes improved input validation.

November 27th – 2 Updates for macOS Sierra 10.12:

  • AppleMobileFileIntegrity had a validation issue where a signed executable could substitute code with the same team ID. Update CVE-2016-7584 added additional validation.

  • FontParser had a buffer overflow in the handling of font files where a maliciously crafted font file could lead to arbitrary code execution. Update CVE-2016-4688 added improved bounds checking.

November 14th – Update CVE-2016-7580 for an issue in macOS Sierra 10.12 Mail where a malicious website could cause a denial of service. This update includes improved URL handling.

November 8th – Critical update APSB16-37 for Adobe Flash Player.  This update contains 9 different CVEs to address a vulnerability that could allow malicious native code to execute without a user being aware.

 

“Do you know the way to San Jose?”

Another cyberattack targets the San Fran Transport Agency.

san fran

Normally the 181 Express to San Jose will cost you about $10 and take about 1 hour and 42 mins. But this weekend you could travel for free, thanks to another demonstration of cybercrime—this one reconfirming the dangers of ransomware and its potentially devastating effects when used against public service networks.

In this case, screens that would normally show train departure and arrival times displayed a message informing users they had been hacked, and that MUNI, San Francisco’s Municipal Transportation Agency, had one more day to pay the bitcoin ransom equivalent to $73K.

While it’s not yet known who’s responsible for the attack, nor exactly how they did it, numerous reports suggest the hacker used the email address previously linked to the Mamba ransomware strain first seen in September 2016.

mamba

A screen at a Muni train station shows the malware message from HDDCryptor. (Click for image source.)

Assuming this attack is linked or similar to Mamba, it’s worth looking at in a little more detail.

Mamba, named after the deadly snake, takes a different approach to encrypting files than other ransomware strains by trying to encrypt the entire drive—not just your data files. This means it’s not just your files but the whole OS, including the master file table, that could get encrypted.

Mamba uses the freeware DiskCryptor software to encrypt your files. It’s highly likely that unaware users are clicking on targeted emails, which download both scripts and the tools to encrypt the drive.

This type of ransomware is perfect for an attack on an organization like MUNI. Why? Unlike other attacks we have seen (like in healthcare), where the encrypted data and personal files are worth big money on the black market, knocking operating systems out at a public transportation agency brings operations to a screaming halt, causing service disruption, revenue loss, and a ransomware fine well worth paying. And what commuters don’t think about while they are enjoying a free ride is that the lost revenue and ransom costs are more than likely going to be recouped through increased commuter costs.

So, in the long run, everyone but the hacker loses out in the aftermath of an attack. That’s why organizations must do more to prevent attacks rather than simply detecting them.

Wherever you are in the world, you probably have organizations, governments, and security authorities providing recommendations on how to protect your organization from threats like Mamba. The FBI, the Australian Signals Directorate, the UK’s National Technical Authority for Information Assurance (CESG), and the SANS institute are just some examples.

These experts all agree that to protect against attack you should:

  • Patch the OS
  • Patch apps (not just Microsoft ones)
  • Remove local administrative privileges from the desktop estate
  • Implement application control or whitelisting to allow only the known good

Shavlik offers a solution that addresses all four of these prevention approaches: Shavlik Patch patches the OS and third-party applications, and Application Manager for SCCM removes local administrative privileges and application control.

November Patch Tuesday 2016

PatchTues-Blog-Nov2016

It’s Election Day! I hope you all voted or will be hitting the polls soon, as this election round has been one for the history books. November 8 also happens to be Patch Tuesday. While this is notably of far less concern than hitting the polls today, Patch Tuesday will be delivering updates from Microsoft, Adobe and Google this month and will, unfortunately, still require your attention tomorrow and in the weeks to come.

Microsoft has released 14 bulletins, six of which are rated as critical, resolving 68 unique vulnerabilities.  Two of the vulnerabilities have been exploited in the wild (Zero Days), and three of the bulletins contain public disclosures.

First off, we will get a little closure on the Adobe Flash/Microsoft Zero Day that was identified in October and to which Flash released an update on October 26 which resolved CVE-2016-7855. Microsoft has resolved CVE-2016-7255 as part of MS16-135.

Adobe has released another Flash Player update (which is rated as a priority one and resolves nine CVEs. If you haven’t already pushed the Flash update from October 26, ( ) this will be a high priority along with MS16-135.

Microsoft has a second Zero Day vulnerability this month (CVE-2016-7256). MS16-132 resolves an open type font vulnerability that can allow an attacker to remotely execute code. An attacker can target a user to exploit this vulnerability by crafting a document designed to exploit the vulnerability or by hosting a specially crafted website designed to exploit the vulnerability. The attacker would need to convince a user to click on or open the specially crafted content, but that’s really not a significant challenge. This bulletin should also be a high priority this month.

There are a number of public disclosures this month across several bulletins, which means enough information has been leaked to the public to give an attacker a head start on developing exploit code.  This increases the risk of exploit occurring for these vulnerabilities so we raise the risk level and priority of bulletins that contain public disclosures. See our Patch Tuesday infographics for more detail.

  • MS16-129 for the Edge browser resolves CVE-2016-7199 and CVE-2016-7209
  • MS16-135 for Windows resolves CVE-2016-7255 (which has already been exploited)
  • MS16-142 for Internet Explorer resolves CVE-2016-7199

Google Chrome went to beta last Wednesday. That along with another Flash Player update means we should expect a Chrome update in the foreseeable future. There is a chance it will come tonight, but it’s more likely to come in the next week. As always you will want to be sure that you have updated Chrome to support the latest Flash Player Plug-In.

If you have not already done so, you will want to make sure to include the Oracle updates from their Q4 CPU that released in October. This included a Critical Java JRE update as well as many other Oracle products.

November also marks the second month of the new servicing model. Here is what you should expect for actual packages to be deployed this month.

The Security Only Bundle (SB16-002) will include the following bulletins: MS16-130, MS16-131, MS16-132, MS16-134, MS16-135, MS16-137, MS16-138, MS16-139, MS16-140 and MS16-142.

The monthly rollup (CR16-002) will include the following bulletins in addition to quality fixes and previous months’ updates: MS16-130, MS16-131, MS16-132, MS16-134, MS16-135, MS16-137, MS16-138, MS16-139, MS16-140 and MS16-142.

As always, we will be running our monthly Patch Tuesday webinar where we will go deeper into the bulletins released and recommendations to prioritize what updates need to be put in place sooner than others. Make sure to sign up for the November Patch Tuesday webinar to catch playbacks of previous months and get access to our infographics and presentations to give you the information you need going into your monthly maintenance. www.shavlik.com/Patch-Tuesday

 

November Patch Tuesday Forecast

windows8patchtuesday

Since October Patch Tuesday there has been a lot of activity. Oracle released their quarterly CPU including an update for Java JRE, Adobe resolved a Zero Day in Flash Player, our tip of the month, and a quick look at what to expect next week as Patch Tuesday hits.

On the Horizon

Actually more of a continuation from last month. On October 17th Oracle released their quarterly CPU including an update for Java JRE resolving seven vulnerabilities. All seven are remotely executable without the need for authentication and three of these have a CVSS score of 9.6. Java was actually on the lower end of total vulnerabilities addressed in an individual Oracle product for this CPU.  Ensure to include this update in your November testing if you have not already deployed it out.

Later in the month Adobe released a Critical Update for Flash Player resolving a Zero Day vulnerability (CVE-2016-7855). On October 26th Adobe released the update for Flash Player (APSB16-36) which started the clock for all the other vendors using the Adobe Flash Plug-In. When a Flash update occurs the plug-ins for Internet Explorer, Firefox, and Chrome also need to be updated.

Firefox uses the NPAPI version of Flash which was also released on the 26th.  The update for Flash for IE (MS16-128) released on October 27th plugging the Flash vulnerability. Google Chrome has two install options for Flash, one which relies on Chrome updating.  If you are using the Pepper Plug-In it was released on October 26th.  If you are using the traditional plug-in, this requires Google Chrome to be updated which occurred on November 1st.

In October, Microsoft changed their servicing model for pre-Windows 10 systems. I covered this extensively in a previous blog post, but there is a little ambiguity with Server 2016’s servicing model options. In a blog post from Microsoft they talk about a Security Only and a Security Quality option each month. This statement specifically caused several people to ask me some questions about how exactly Microsoft is handling updates on Server 2016.

“You can then have the flexibility to choose the security only update, or the quality update to build your patch management strategy around.”

The reality right now is Server 2016 updates are exactly like Windows 10. Cumulative bundles that include all updates that came before.  It will be interesting to see if a Security Only option does make itself available in November or sometime in the near future.  I expect a number of Microsoft customers would appreciate Security Only as an option for Server 2016.

Patch Management Tip of the Month

Exceptions: You can never push all patches. There is always an update that will conflict with business critical apps which cause exceptions. Documenting these exceptions and the reason they occurred is very important, but documenting an exception is just the beginning.

With each exception you are increasing risk. Each exception is an exposure that will potentially allow malware or ransomware into your environment or allows a threat actor to gain a foothold or move closer to proprietary information or user data.  With an exception you should also identify mitigating steps to reduce the risk. This may come in many forms, but here are some examples:

  • Least Privilege Rules will often mitigate the impact if an attacker is able to exploit a vulnerability. If you take a look at our Patch Tuesday infographics on our Patch Tuesday page you will see a column labeled “Privilege Management Mitigates Impact”.  These vulnerabilities will only gain the attacker equal rights as the user who is exploited.  If they are a full Administrator the attacker gains pretty much full access to the system. If they are running reduced privileges then the attacker must use an escalation of privilege vulnerability to gain sufficient permissions to do more.
  • Application Control will allow you to control what applications can be installed or run on a system and can effectively block most malware, ransomware, and other forms of attack. Application control can take many forms like Whitelisting or Blacklisting. These would be static application controls. More dynamic forms would include Trusted Ownership or Trusted Vendor rules. These are significantly easier to implement and maintain and also allow you to more easily rollout an effective Application Control Policy. The dynamic approaches are less commonly found, but we have a solution that can help there.
  • Containerization can effectively contain the more highly vulnerable user experiences like browsing the web and accessing email. Anything that occurs during these user experiences happens in a virtual container. If you have an exception on the system that is exposed by a phishing attack or drive by download the malicious payload whether a malvertising attack, ransomware, or some other form of malware would execute in the container and be separated from the physical system. Close the container (Browser or email, etc) and the threat goes away.

There are many other strategies to reduce exceptions from exposing too much risk like moving the sensitive application into a virtual environment and locking down access to that system to only require users, but this gives you some ideas. With every exception we recommend documenting the reason why it was made and the additional steps taken to reduce risk to the system.

Your Patch Tuesday Forecast

We are less than a week away from Patch Tuesday and as you can see there is a significant buildup of issues to deal with already. I would forecast that the 3rd party front is going to be lighter than normal for Patch Tuesday and we can expect an average workload from Microsoft on the order of ten or so bulletins total being released.

As always, join us for our Monthly Patch Tuesday Webinar next Wednesday November 9th as we delve deeper into the bulletins and vulnerabilities resolved on Patch Tuesday.

 

 

 

 

Latest Updates for macOS Sierra and more…

Early last week Apple released update 10.12.1 for macOS Sierra, Security Update 2016-002 for El Capitan, and Security Update 2016-006 for Yosemite.  Updates were also released for 10.0.1 Safari and 10.1.1 for iOS. These updates were released just in time for an Apple hosted Mac-centric product event.

With update 10.12.1 for macOS Sierra being the first update available to Sierra since it was released, there are a number of fixes included for some of the most pressing issues identified in this latest operating system. Here are some of the fixes that are available with the 10.12.1 macOS Sierra:

  • An automatic smart album in Photos for Depth Effect images taken on iPhone 7 Plus
  • Improved compatibility between Microsoft Office and iCloud Desktop and Documents
  • Improved security and stability in Safari
  • Improved reliability of Auto Unlock with Apple Watch
  • Fixed issue where mail was prevented from updating when using a Microsoft Exchange account
  • Fixed issue where text was sometimes pasted incorrectly when using Universal Clipboard

macOS Sierra/El Capitan/Yosemite

macOS Sierra 10.12.1 includes fixes for 14 vulnerabilities, 2016-002 El Capitan includes fixes for 8 and 2016-006 Yosemite includes fixes for 5.

Many of the vulnerabilities relate to escalation of privilege, arbitrary code execution, information disclosure. Some of the more interesting vulnerabilities include:

  • CVE-2016-4661: An application may be able to cause a denial of service.
  • CVE-2016-4675: a libxpc component vulnerability where a local application may be able to execute arbitrary code with root privileges.
  • CVE-2016-4669: A local user may be able to cause an unexpected system termination or arbitrary code execution in the kernel.

These examples are noteworthy because they are often used as the starting point to exploiting a system through social engineering. Once the hacker has access, the other vulnerabilities may be useful to gain additional access or information.

Safari 10.0.1

This update includes fixes for 4 vulnerabilities, all of which address the issue where processing malicious web content may lead to arbitrary code execution.  Since these vulnerabilities have to do with users visiting bad websites or web ads which may result in running malware, this update should be applied on all systems.

iOS 10.1.1

This update includes fixes for 17 vulnerabilities, one of which was just added today. These vulnerabilities span issues from arbitrary code execution to the leaking of sensitive user information.

Summary

It is highly likely that additional fixes will be added to the iOS update in the upcoming days. You can also expect to see a macOS Sierra 10.12.2 update released to the general user base real soon since the macOS Sierra 10.12.2 update is already in beta.

What’s in a Name: Why We’re Changing Our Name (and More) in 2017

BLOG-whats-in-a-nameIn the timeless classic Romeo and Juliet, Shakespeare wrote, “What’s in a name?”

This famous line implies that names are simply labels that don’t really matter. After all, Juliet posits, “A rose by any other name would smell as sweet. It’s a nice sentiment, but perhaps (like Juliet) a bit naïve.

If a rose were called skunk weed, you would expect a very different experience when you smelled it. And as Romeo and Juliet’s tragic tale demonstrates, names can unite or divide us.

Names matter.

So what does this have to do with Shavlik?

We’re changing our name in 2017.

As you know, Shavlik was acquired by LANDESK a few years ago. LANDESK is a strong, stable and well-respected company in the IT industry. Our technologies are known for just working. This means being reliable, easy to integrate and use alongside other IT systems, and giving IT the ability to get the job done—whatever that job is—particularly when it comes to operational IT and remote enterprise systems management.

Add to that the fact that our staff is known for being friendly, willing to listen, and quick to act to make our customers’ lives easier, and we’ve got ourselves a great name and an equally great brand reputation.

So if the name is so great, why would we want to mess with it?

We wouldn’t, except that…

In recent years, LANDESK has continued to organically develop and enhance our technology, extending and integrating it in the directions of unified endpoint management (the management of traditional and mobile devices from a single platform) and endpoint security configuration management.

In addition to Shavlik, LANDESK has acquired several companies that have significantly expanded our focus to include IT disciplines such as:

  • IT service management (TouchPaper)
  • IT asset management (Managed Planet)
  • Patch management (Shavlik)
  • Enterprise-class, ruggedized mobile device management and application streaming (Wavelink and Naurtech)
  • Mobile email security (LetMobile)
  • Business value dashboards and reporting for IT (Xtraction)
  • User environment management for physical and virtual devices, as well as application management and privilege management (AppSense)

They’ll all change too. All these companies will have only one name in 2017. Does this change our relationship with Microsoft? Nope. Not at all.

Over the next several months, you will start to notice changes in LANDESK and the brands we’ve acquired. We are evolving. Refining our focus. Transforming in ways we never have before. And we want to bring our customers with us, continuing to help you along your organization’s journey to IT maturity.

We will still be the great company you’ve come to know and trust. We will continue to develop and maintain the world-class IT solutions relied upon by organizations across the globe. But we will be coming together in new ways, under a new company name, and with a new focus.

CyberSecurity Awareness Month: CyberSecurity Tips for Road Warriors

GettyImages-537708180

Security Tips for Road Warriors

A couple months ago one of our product evangelists reached out to me and asked how to better protect himself and his personal information in his travels.  As he settled into a hotel and a day later saw it in a headline as one of the latest exposed to credit card theft he felt a bit exposed.  I would have loved to tell him some magical tips that would 100% safeguard him from that day forward, but in short, you cannot prevent it.  There is no way to know who the next breach target it or when the breach could have been occurring.  The only guarantee you have is that another breach will occur and odds you will have used your card there at some point.  You can, however, reduce the impact when any of your information does get nabbed.  Now, you can go to extremes.  Cancel all credit cards, just use cash, close all of your social media and online accounts of all kinds, but nobody wants to live that way either.  The key is balancing the risks.  I talked to many road warriors within our own company and we have some tips and tricks that can help you out.  Our road warriors range from my light 16-20 weeks or so of travel per year to Simon, Doug and Rob who spend more than 50% of their year on the road and take us to all parts of the globe.  Here are some of the tricks we use to safeguard ourselves and to mitigate the impact if our information becomes exposed.

Phil Richards, Chief Security Officer:

I recommend reporting your credit card as stolen/lost/missing to the credit card issuing company at least annually.  This allows you to receive a new credit card number, and invalidates the old one. Many hotel chains and retailers that have had credit card info breaches. For the road warrior, it is highly likely that your card is among them.  By changing the CC number, the stolen information is useless and cannot harm you.

Rob Juncker, VP of Engineering:  

I never go anywhere without my HooToo.  It’s a wall charger with 2 USB ports, an Ethernet port, a fully portable charger (so it’s like a power brick) and embedded router.  The best part about this device is it has full router capabilities.  I have it setup so my computer always connects to it, and then I bridge the hotel Wifi to my personally secure wifi, or use the Ethernet port to plug into the hotel jack.  – I have it set by default to disable all inbound and just allow outbound.

Doug Knight, VP of Systems Management:

For the record, I told Rob about the HooToo, but since he beat me to it here is a tip for additional layers of security and anonymity if your travels take you to countries where you need some extra protection and ability to bypass some levels of content filtering. I subscribe to a VPN service called Private Internet Access.  I setup a L2TP and then run their default client on top of that.  The IPSEC client gives me encryption and some anonymizing and the L2 VPN even allows me to get thru (pretty reliably) the “Great Firewall of China” to reach content that may otherwise be blocked. For the server setting in the L2TP VPN, it’s best to enter the IP address for the server locale you wish to access instead of the DNS name. To obtain an IP address for this purpose, you can ping it or you can go to http://www.ping.eu/ping and enter the server name to be able to get IPs for the server you would like. Do this before you leave the country.

Simon Townsend, Chief Technologist:

I don’t just evangelize about the great security solutions we have at AppSense.  I use them regularly.  I run as a standard user on my Windows machine and have a local admin account that is used only for installation and initial setup.  I run AppSense Application Manager on my system and by default cannot install or run anything that I download under the context of my own LANDESK account.  If I need to install something locally I use RunAs or AppSense self-elevation to give myself temporary permission to perform those actions.  If I need to do something that is only going to be temporary I will bring up a VM snapshot that is NAT’d.  This provides a Deep Freeze style solution that I can revert easily and separates the task I am performing from local data as it would not be exposed to the VM.

Chris Goettl, Senior Product Manager:

You never know what is observing traffic on public wifi or if the connection you are on has been compromised.  Early in my career I connected to a hotel wifi and their router had been compromised.  My Gmail session was hijacked by a man in the middle attack and within a few hours suspicious email began flooding forth from my account.  Needless to say I changed my password, enabled two factor authentication (also highly recommended) and became infinitely more paranoid during my travels.  Now wherever I go, after connecting to the hotel wifi I immediately connect to the corporate VPN before connecting to email or opening my browser.  The VPN tunnel provides an additional layer of encrypted protection from prying eyes.  I have also just ordered a HooToo and will be adding that to my travel defenses.

 

October 2016 Patch Tuesday

201610-infographic-Shavlik-Patch-October-sm

October Patch Tuesday will see some changes to how Microsoft and Adobe will be distributing updates.  There is a lot of buzz regarding Microsoft’s servicing changes to pre Windows 10 systems. October Patch Tuesday is the first release under this new servicing model, which we will talk about more in a moment.  There are a few changes for Adobe Flash Player starting this month that you will need to be aware of. We are expecting a Google Chrome release today and Oracle’s Quarterly CPU next week, so plan on updates for Java JRE and many other Oracle solutions.

Regarding Microsoft’s servicing model changes, Microsoft has basically consolidated all IE and OS bulletins into a single update. This will be served up in one of two ways: as a security only quality update or a security monthly quality rollup. The biggest difference between these is the security only is bundling each month’s security updates only. The rollup includes non-security fixes as well as being cumulative. I recently spoke with LANDESK CSO Phil Richards about this change and he provided some good feedback as far as the challenges companies may face. In last week’s Patch Tuesday Forecast, I also talked about some recommendations on how best to choose between the security only and the rollup options.

Adobe has changed their distribution for Flash Player, so you would need to get an agreement in place with Adobe to be able to get access to the Flash Player distribution page. Today also marks the final release of Flash Player ESR. So instead of a current branch and stable branch, Adobe will just have current branch. Since they are doing fewer feature changes to Flash Player, having a single branch simplifies their release model. The new distribution page included this notification:

flashesr

Oracle’s Quarterly CPU is coming next week on the 18.  Oracle releases on the first month of each quarter on the Tuesday nearest to the 17, which typically falls the week after Patch Tuesday. Watch for an update next week for Java and many other Oracle products.

Google Chrome should be releasing today. The Dev channel for Chrome Desktop updated late last week which usually indicates a Chrome release on Patch Tuesday or soon after. With a Flash Player update, they will be releasing to support the latest plug-in, but likely will have some additional security fixes as well.

Let’s break down the more severe of these bulletins.

Looking at the infographic you would see that Microsoft has released 10 bulletins today — five of which are rated as critical — and there are four unique Zero Day exploits across five of the bulletins. Now there are 10 bulletins, but the actual number of deployable packages is less. There will be the security only or security rollup, which will bundle MS16-118, MS16-120, MS16-122, MS16-123, MS16-124, MS16-125 and MS16-126 together in a single installer. For systems where you have installed a newer version of .Net you will have the .Net Rollup. Skype, Lync, Office and Flash are separate updates yet. So you could have as many as seven packages to deliver to some endpoints, but most will be getting around five actual packages to test.

MS16-118 is a critical update for Internet Explorer. This bulletin resolves 11 vulnerabilities including one Exploit in the Wild (CVE-2016-3298). There are multiple vulnerabilities in this bulletin that are user targeted, meaning the attacker can convince a user to open specially crafted web content to exploit the vulnerabilities. Several of the vulnerabilities can also be mitigated if the user is running as less than a full administrator, the attacker would only gain equal rights to the user reducing the impact if exploited.

MS16-119 is a critical update for Edge browser. This bulletin resolves 13 vulnerabilities including one Exploit in the Wild (CVE-2016-7189). Many of the vulnerabilities resolved in this bulletin are user targeted. An attacker who successfully exploited the vulnerabilities could gain the same user rights as the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than users with administrative user rights.

MS16-120 is a critical update for .Net Framework, Office, Skype for Business, Lync and Silverlight. The bulletin resolves seven vulnerabilities including one Exploit in the Wild (CVE-2016-3393). This bulletin includes vulnerabilities that are user targeted. An attacker can host specially crafted web content or specially crafted document file designed to exploit the vulnerabilities. One of the vulnerabilities (CVE-2016-3396) can also be exploited through the Outlook Preview Pane. Users running with reduced privileges could reduce the impact if exploited.

MS16-121 is an important update for Office. The bulletin resolves one vulnerability, which has been Exploited in the Wild (CVE-2016-7193).  An attacker could craft a file to send through email or by specially crafting web content designed to exploit the vulnerability. Users running with reduced privileges could reduce the impact if exploited.

MS16-122 is a critical update for Windows. The bulletin resolves one vulnerability. An attacker could exploit this vulnerability by convincing a user to open a specially crafted file from a webpage or an email message. The Outlook Preview Pane is an attack vector for this vulnerability. Users running with reduced privileges could reduce the impact if exploited.

MS16-126 is a moderate update for Windows. The bulletin resolves one vulnerability, which has been Exploited in the Wild (CVE-2016-3298). This is the same CVE ID as the Exploit in MS16-118 for Internet Explorer. To fully resolve the vulnerability, both MS16-118 and MS16-126 must be installed. For Windows Vista and Server 2008, this means installing two separate packages. For newer Oss, both will be included in the security only or security rollup package.

MS16-127 is a critical update for Flash Player for Internet Explorer. This update resolves 12 vulnerabilities in Adobe Flash Player Plug-In for Internet Explorer. To fully resolve Flash Player vulnerabilities you must install updates for Flash Player, Flash for IE, Flash for Chrome and Flash for Firefox, so this could be multiple installable updates on a single system.

APSB16-32 is a priority one update for Adobe Flash Player. This update resolves 12 vulnerabilities. Many of the vulnerabilities are user targeted and, if exploited, could allow an attacker to take control of the affected system.

For more in depth analysis and conversation regarding this Patch Tuesday, join us for the Shavlik Patch Tuesday Webinar tomorrow morning.

 

 

Patch Tuesday Forecast October 2016

windows8patchtuesday

October is here already and should be an interesting lineup of updates coming in the next few weeks.  There are also some things you need to know about servicing model changes from Microsoft and on distribution changes for Adobe Flash. Oracle is also going to be dropping their quarterly CPU this month.  Read on for more details:

On the Horizon

This is the month Microsoft will have its first delivery under the new servicing model and there is a lot of uncertainty amongst companies as to what really is going to change. I interviewed LANDESK CSO Phil Richards on the subject and he had a lot to say. You can check out the full interview here, but it boils down to this:

  • Microsoft’s change, while well intentioned, will impact many companies and could lead to some hard decisions.
  • Application compatibility is going to be the most significant of these changes. Most companies know what products are sensitive to updates already, so it may not be a bad idea to reach out to those vendors in advance and start asking if they understand the changes coming and potential ramifications.
  • While there may be some hard decisions in the future, with planning and other security measures the problems can be overcome.

Oracle will be releasing their quarterly critical patch update this month. I always try to emphasize this as they will not release on Patch Tuesday, but on the following Tuesday. Oracle’s release schedule is the first month of each quarter on the Tuesday closest to the 17, which falls to Tuesday October 18 this month. The Oracle CPU always brings a lot of fixes for some pretty nasty vulnerabilities. Take July’s release for JRE. This update included 13 security fixes, nine of which were remotely exploitable without authentication. Four of these updates were rated as CVSSv2 9.6, are exploitable remotely without authentication, are rated as low complexity, meaning they are easier to exploit, and rate as high for confidentiality, availability and integrity. According to analysis by Verizon’s 2015 Data Breach Investigations Report, these would fit the pattern of vulnerabilities likely to be exploited within two weeks of release from the vendor.

Adobe has changed availability of Flash Player for distribution. This change has been looming for some time now. We first caught wind of this late last year and since they have pushed the date multiple times, but September 29 they finally took the plunge. From the distribution page you now get two directions to go: for consumers and for companies wanting to distribute. Follow the link to request approval for distribution. I personally went through the process and it was quick and painless and, once approved, you will receive details on how to access the enterprise-ready version of Flash Player for distribution in corporate environments.

Patch Management Tip of the Month

In a conversation I had yesterday with one of our customers, we shared details of the change Microsoft described in its blog and through other sources like the customers Microsoft TAM and talked through some scenarios to figure out a plan to proceed this month and going forward. Here is where we left the conversation understanding full well that “No plan survives contact with enemy.”

  • For systems currently in operation plan to test and rollout the October security bundle, which will include updates for IE and the OS in a single package. This package should be security-only updates and also should not be cumulative. In other words, if you need to exclude this bundle for any reason, you should be able to take November’s security bundle without it forcing application of the October security bundle. Expect to take the security bundle each month until you hit a situation where non-security updates (bug fixes) would force the need to apply the cumulative rollup.
  • For new systems implemented after the servicing model change, they are planning to start with the cumulative rollup until a point where they hit an exception, in which case they would switch to the security bundle for those systems until the event which caused the exception can be resolved, allowing application of the cumulative rollup once again.

And I will re-emphasize last month’s tip which is to expand your pilot group for application compatibility testing. Getting power users from the parts of your organization that rely on business critical apps will help you to ensure that these larger bundles of updates do not cause impacts earlier in the test process.  Many companies have test systems, but only validate some high level functionality like login to the system and basic data rendering. Many issues could occur deeper in legacy apps from rendering of PDFs to printing documents, etc. This year alone we have seen both PDF and GDI updates nearly every month from Microsoft. These are common components to be updated as they are high profile targets for user targeted attacks like phishing scams. A vulnerability exploiting a user is often the first point of entry into a company’s network.

Your Patch Tuesday Forecast

From this point on you can expect an average of three to four Microsoft updates. Under the new servicing model, we will typically see the Security Bundle (IE and OS updates), Flash for IE, .Net, Office and occasionally Sharepoint, SQL, Exchange and other applications.

Oracle will release on October 18, so expect a critical update for Java and many other Oracle solutions.

Adobe is due for an Adobe Acrobat and Reader update, so I am forecasting at least two bulletins from Adobe this month. Adobe Reader and Flash Player with likely use Acrobat as well. If Flash drops we will see the Flash for IE bulletin from Microsoft and plug-in updates for Google Chrome and Mozilla Firefox.

It has been nearly a month since the last Google Chrome release on September 15. They did a re-release late in the month, but with only a minor change. The beta channel for Desktop was updated yesterday so we are not far off. There is a good chance we will see a Chrome update on or before Patch Tuesday.

And as always, watch for our Patch Tuesday update and infographic next Tuesday and catch deeper Patch Tuesday analysis on our monthly Patch Tuesday webinar next Wednesday. Sign-ups and info can be found on our Patch Tuesday page.

The CSO Perspective: On the Upcoming Microsoft Service Model Change

Cybersecurity(Own)

The CSO Perspective: What Does the Microsoft Servicing Change Mean?

October is CyberSecurity Awareness month. It’s also the month that Microsoft will implement the new servicing model to pre-Windows 10 systems. Yes, that’s correct. Windows 7, 8.1, Server 2008 R2, 2012, and 2012 R2 will all be moving to an update servicing model similar to Windows 10. Microsoft first announced this change in June and described it as follows:

  • Internet Explorer and Operating System updates will be packaged in two ways.
    • Security Bundle—All OS and IE (Security only) updates for the month will be bundled in a single update. This is not cumulative: the November Security bundle would not include the October Security updates.
    • Cumulative Update—All OS and IE updates for the month for both security and non-security are included in a cumulative rollup each month. The November rollup would include the updates from the October cumulative update.
  • .NET Framework will be a separate Cumulative Rollup. This update will be a single package no matter how many .NET versions are currently installed on a system. The installer will detect and update the installed versions. It will NOT install net new versions.
  • Adobe Flash for IE will be a separate update.
  • Office, SharePoint, Exchange, SQL, and other products will still be separate updates each month.

I’ve had questions from customers, prospects, writers, vendors, and partners about the real impact of this. I’ve posted my thoughts, but today I thought we would catch up with LANDESK CSO Phil Richards and get his.

Chris: Phil, thanks for taking the time to talk about how you see this change and the improvements and challenges we’ll face in the future.

Phil: Thanks, Chris. This is an interesting development from Microsoft that has potential security improvements, and potential issues, depending on how we, the consumers, respond.

Chris: Phil, Microsoft’s change was prefaced with a message of “You asked for it, we delivered.” They didn’t really say what we “Microsoft customers” asked for. So, based on the changes, what was it you think we asked for?

Phil: Enterprise-level patching is far more complex than patching your personal computer at home. There are three main improvements customers are looking for over today’s patching processes: simplification, quality, and security. I think a good portion of the consumers are looking for a simplified patching experience. The complexity of patching—understanding precedence requirements, identifying installed components that require patching, and anticipating future patch needs—makes the patching experience somewhat painful, error prone, and manually intensive for IT professionals. Unfortunately, this is a double-edged sword: when Microsoft bundles the patches, making the customer interface more simplistic, they increase internal complexity of the patch package. he bundled patches must respond correctly to more configuration permutations. While many customers don’t like the complexity associated with multiple patches, I believe they will be unable to support patch bundles across the entire set of systems that require patching. When an IT department has a particular server that needs special handling because of software that will not work with a specific patch, it’s faced with the very real challenge of not applying the entire patch bundle on that system. Over time, we will see many systems that are not able to take patches at all, lowering the security readiness of the enterprise.

Customers are also asking that Microsoft improve the quality of the patches. But increasing the complexity of the patch package by bundling patches raises quality of the Microsoft package at the cost of adversely impacting other sensitive applications on the system.
Finally, customers also need improved security from their patches. With this new patching delivery method, updates are more frequent and potentially more comprehensive. Unfortunately, security updates often create new security vulnerabilities as quickly as they patch old ones. They are, after all, software. While this happens much more frequently with other providers, it has occurred with Microsoft patches. Another security issue has to do with the volume of patches and the possibility of missing one or more them in your environment. By bundling the patches and providing a cumulative update, IT professionals have the ability to make sure their servers are up to date. Again, the downside is that if I am unable to patch a particular server because of one component, the server remains vulnerable to all threats in the whole patch package.

Chris: Seems like, even with Microsoft’s good intentions, there could be challenges. Digging deeper into some of your points, let me throw a hypothetical situation at you and see how you’d handle it. Let’s say you have a legacy application in your environment that’s critical to your business and very sensitive to patching. You know that each month the security updates need to be tested and often result in one or two OS updates you have to mark as exceptions because they conflict with this application.

If we look at September’s updates and apply the details Microsoft described, the 14 bulletins become 4. The largest is for IE and OS updates. It rolls 10 bulletins and 31 vulnerabilities into a single bulletin. There is another for Office, one for .NET, and one for Flash Player for IE. One of those OS bulletins for September is for the Windows Graphic Components. Under the old model it’s bulletin MS16-106, which resolved 5 vulnerabilities. In this case it will be in the bulletin that includes 31 vulnerabilities, including a Zero Day that was resolved in IE. This GDI change breaks the legacy application and will cause a major disruption to the business. You have to choose to make an exception or break the application and wait for the vendor to fix it. What would you choose to do?

Phil: If I choose to run the critical business application and keep my business afloat, I have to choose not to install multiple patches, which poses a very real threat to my business. If I choose to patch, I have to stop running the application, which poses a very real threat to my business. To address this issue, I’d try to get the vendor of the application to make modifications to support the Microsoft patch. I’d also look at other technologies that will allow me to further isolate the offending application, so I can patch the operating system, or apply network configuration changes to decrease the attack surface of the server. Major technologies in this space include containerization to isolate the application or web application firewalls to decrease the attack surface. While there are workarounds to patching issues, these require heavy lifting by an already overburdened IT organization. These workarounds aren’t efficient and will increase complexity of the environment overall—which is exactly what Microsoft is trying to avoid in the first place.

Chris: Let’s take this scenario one step further. The legacy application is from a vendor that’s no longer in business, so there’s no fix forthcoming. This leaves you with a known exploit for IE exposed in your environment, which is unacceptable. What steps would you take to protect the systems that require this application?

Phil: At this point, the best that can be done is application isolation through containerization and network isolation through a combination of segmentation, firewalls, and web application firewalls. The amount of work involved in this one-off solution is significant, and it’s brittle. I believe this scenario will happen multiple times for customers that have special apps not supported by vendors that are running significant portions of the business. Once the workaround solutions are in place, there is no incentive to fix the underlying problem. It just becomes more walled off, creates higher technical debt, and because of the brittleness of the solution, remains a high risk area of the infrastructure. The problem also compounds. Since the patches need to be cumulative in nature, there is the possibility that by skipping the patch bundle for October, you might not be able to take patches in the future, which increases the network configuration pressure, increases the brittleness of your workaround, and makes it all the more difficult to extricate your business app from the vicious cycle.

Chris: Great feedback, Phil. Thanks again for your time and recommendations. It appears that we should all expect some changes in the near future and some hard questions may come up, but I think you have provided some great takeaways from this discussion.

  • Microsoft’s change, while well intentioned, will impact many companies and could lead to some hard decisions.
  • Application compatibility is going to be the most significant of these changes. Most companies know what products are sensitive to updates already, so it may not be a bad idea to reach out to those vendors in advance and start asking if they understand the changes coming and potential ramifications.
  • While there may be some hard decisions in the future, with planning and other security measures the problems can be overcome.

As always the team here will be keeping a close eye on the situation. As we near October Patch Tuesday we will have more details to share. Make sure to sign up for the October Patch Tuesday Webinar; we plan to cover the new servicing model changes in detail once we see the first month of the new model in operation. www.shavlik.com/Patch-Tuesday