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.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/13/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Mobile App Fraud Jumped in Q1 as Attackers Pivot from Browsers
Jai Vijayan, Contributing Writer,  7/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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 Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14174
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view titles of a private project via an Insecure Direct Object References (IDOR) vulnerability in the Administration Permission Helper. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5....
CVE-2019-20901
PUBLISHED: 2020-07-13
The login.jsp resource in Jira before version 8.5.2, and from version 8.6.0 before version 8.6.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect in the os_destination parameter.
CVE-2019-20898
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.
CVE-2019-20899
PUBLISHED: 2020-07-13
The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.
CVE-2019-20900
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the Add Field module. The affected versions are before version 8.7.0.