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.

Perimeter

8/10/2010
04:49 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
US Counterintelligence Director & Fmr. Europol Leader Talk Election Security
Kelly Sheridan, Staff Editor, Dark Reading,  10/16/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26895
PUBLISHED: 2020-10-21
Prior to 0.10.0-beta, LND (Lightning Network Daemon) would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation (e.g., routing node, payment-receiver,...
CVE-2020-26896
PUBLISHED: 2020-10-21
Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collis...
CVE-2020-5790
PUBLISHED: 2020-10-20
Cross-site request forgery in Nagios XI 5.7.3 allows a remote attacker to perform sensitive application actions by tricking legitimate users into clicking a crafted link.
CVE-2020-5791
PUBLISHED: 2020-10-20
Improper neutralization of special elements used in an OS command in Nagios XI 5.7.3 allows a remote, authenticated admin user to execute operating system commands with the privileges of the apache user.
CVE-2020-5792
PUBLISHED: 2020-10-20
Improper neutralization of argument delimiters in a command in Nagios XI 5.7.3 allows a remote, authenticated admin user to write to arbitrary files and ultimately execute code with the privileges of the apache user.