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.


04:49 PM
John H. Sawyer
John H. Sawyer

Protecting Your Network From The Unpatchable

When I first saw the F-Secure blog post on installing Microsoft's fix for the LNK vulnerability on a Windows XP SP2 host, I couldn't help but ask, "Why?" Seriously. Why would anyone running a Windows XP host not be running with the latest service pack and security updates? And then it hit me.

When I first saw the F-Secure blog post on installing Microsoft's fix for the LNK vulnerability on a Windows XP SP2 host, I couldn't help but ask, "Why?" Seriously. Why would anyone running a Windows XP host not be running with the latest service pack and security updates? And then it hit me.We're surrounded by systems that can't be patched because they are vendor-managed systems, laboratory machines, medical devices, and embedded systems. They are stuck at a particular operating system version and patch level due to a variety of reasons:

  1. The vendor doesn't support any third-party software loaded by anyone else by the vendor. Loading third-party software can void the warranty because it hasn't been tested for compatibility.
  2. The laboratory hardware connected to the computer requires a special driver or software that only runs on Windows 3.1 or 95. Upgrading the computer to XP or Windows 7 requires purchasing a new software license that is "too expensive."
  3. The vendor using an embedded operating system from another vendor that you don't have access to in order to install patches or turn off vulnerable services.
I've seen cases where case #1 affects what security software can be installed. Host-based firewalls could not be deployed, so network firewall rules had to be put in place to protect the host. One particular vendor would not allow any antivirus or host-based intrusion detection software be installed except for Cisco Security Agent-which had it's End-of-Sale and End-of-Life announcements made a couple months ago.

Case #2 is a touchy subject for some. From the security standpoint, I want to recommend that they pony up the bucks and buy the new version of the software and/or hardware. However, having the academic background that I do, I know it can be difficult for researchers to shell out tens of thousands of dollars to make that purchase.

I think we're seeing a perfect example of case #3 with the recent VxWorks vulnerabilities. I've spoken to several friends who've called their vendors looking for a fix to vulnerabilities they've identified on their networks using the Metasploit Framework's scanning module or the new Nessus plug-in. The vendor ends up forwarding the call to numerous other people who have no idea that their printer, Fiber Channel switch, or other device even runs VxWorks.

So what are we as security professionals left to do when faced with these unpatchable systems? We could be jerks and force them all to be unplugged. Or we could work with the individuals who use them daily so as to not impact their productivity while protecting them and our network.

For example, you should segment these devices from the rest of the network. If they don't need Internet access, don't let them have access, or if they do, force them through a highly restrictive proxy. If they don't need to be on the network, then remove their NICs or fill the ports with epoxy.

There are many ways to approach it, but the key is to work with IT and the uses to come up with usable scenarios that allow productivity while maintaining security. And when it comes time to replace the device, find a new vendor.

F-Secure: How to Install LNK Update (KB2286198) on Windows XP SP2

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.


Recommended Reading:

Comment  | 
Print  | 
More Insights
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.