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.

Comments
Can Your Patching Strategy Keep Up with the Demands of Open Source?
Newest First  |  Oldest First  |  Threaded View
timintech
50%
50%
timintech,
User Rank: Author
6/19/2019 | 10:05:28 AM
Re: On Open Source, Freeware and other slithy toves
My core point being that open source components are likely throughout your environment, not just in a test area. That's in large part due to the types of problems solved. So, if you look closely at any firmware, you'll likely see open source components in there. The same goes for virtualization and containerization software or public cloud infrastructure. Even Microsoft is a huge supporter of open source with over 2500 projects published on GitHub and .Net Core available under an MIT license.

Net of this, you're absolutely right that a risk reward tradeoff is required – it's just that with the ubiquity of open source usage in commercial applications, you're going to want to ensure you know what's being used or embedded regardless of where it originated.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
6/19/2019 | 8:40:28 AM
Re: On Open Source, Freeware and other slithy toves
i neglected to comment that some open source or shareware can be VERY VERY useful, performing short-cut work that off the shelf applications do not and, by that virtue, are beloved.  That said, IT professionals then have to weigh the risk-reward equation on this product.  Is it worth the ease of task vs. ease of infection and lack or difficulty of patching resources.   There is also the severity of platform mount - is the software on a non-important system or a critical host server.  Some of it is just grand for programming.  Single workstation, ok, a threat point but not a server.  So it is a balance act between threat and gain. 
timintech
50%
50%
timintech,
User Rank: Author
6/18/2019 | 3:31:35 PM
Re: On Open Source, Freeware and other slithy toves
The most interesting thing we see when auditing an application is how strongly some teams hold on to the perception there is no, or at best limited, use of open source technologies in their applications or environments. The reality is that open source is part of most modern applications – be it in the app itself or how its deployed. Not knowing what you've got is the easiest way to get blind-sided. That's why the patch management strategy is so crucial, and if you'd prefer a patch Tuesday type model, there are many vendors out there who'll happily provide that type of service for a license/support fee. Just be careful to get that complete inventory so you can ensure full compliance from all vendors - otherwise that 50s Olds experience could be the result!

 
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
6/18/2019 | 2:31:15 PM
On Open Source, Freeware and other slithy toves
I have liked shareware ages ago because it was fun and generally free.  These days it is also wide open available and as an open door product, I have never considered for use in a corporate environment.  Rather like having an old 1950's Oldsmobile in the back yard - easy to break into.  It just is a risk by itself and patching is the next nightmare, point of this article.  Indeed you have to devote some resource and time to patching - no Patch tuesday here.  It just never struck me in the right vein and, today, I have none of it at all.   


I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5087
PUBLISHED: 2019-11-21
An exploitable integer overflow vulnerability exists in the flattenIncrementally function in the xcf2png and xcf2pnm binaries of xcftools 1.0.7. An integer overflow can occur while calculating the row's allocation size, that could be exploited to corrupt memory and eventually execute arbitrary code....
CVE-2019-5509
PUBLISHED: 2019-11-21
ONTAP Select Deploy administration utility versions 2.11.2 through 2.12.2 are susceptible to a code injection vulnerability which when successfully exploited could allow an unauthenticated remote attacker to enable and use a privileged user account.
CVE-2019-6693
PUBLISHED: 2019-11-21
Use of a hard-coded cryptographic key to cipher sensitive data in FortiOS configuration backup file may allow an attacker with access to the backup file to decipher the sensitive data, via knowledge of the hard-coded key. The aforementioned sensitive data includes users' passwords (except the admini...
CVE-2019-17272
PUBLISHED: 2019-11-21
All versions of ONTAP Select Deploy administration utility are susceptible to a vulnerability which when successfully exploited could allow an administrative user to escalate their privileges.
CVE-2019-17650
PUBLISHED: 2019-11-21
An Improper Neutralization of Special Elements used in a Command vulnerability in one of FortiClient for Mac OS root processes, may allow a local user of the system on which FortiClient is running to execute unauthorized code as root by bypassing a security check.