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.   


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3454
PUBLISHED: 2021-10-19
Truncated L2CAP K-frame causes assertion failure. Zephyr versions >= 2.4.0, >= v.2.50 contain Improper Handling of Length Parameter Inconsistency (CWE-130), Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-fx88-6c29-...
CVE-2021-3455
PUBLISHED: 2021-10-19
Disconnecting L2CAP channel right after invalid ATT request leads freeze. Zephyr versions >= 2.4.0, >= 2.5.0 contain Use After Free (CWE-416). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7g38-3x9v-v7vp
CVE-2021-41150
PUBLISHED: 2021-10-19
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is c...
CVE-2021-31378
PUBLISHED: 2021-10-19
In broadband environments, including but not limited to Enhanced Subscriber Management, (CHAP, PPP, DHCP, etc.), on Juniper Networks Junos OS devices where RADIUS servers are configured for managing subscriber access and a subscriber is logged in and then requests to logout, the subscriber may be fo...
CVE-2021-31379
PUBLISHED: 2021-10-19
An Incorrect Behavior Order vulnerability in the MAP-E automatic tunneling mechanism of Juniper Networks Junos OS allows an attacker to send certain malformed IPv4 or IPv6 packets to cause a Denial of Service (DoS) to the PFE on the device which is disabled as a result of the processing of these pac...