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.

Application Security

10/6/2020
10:15 AM

6 Best Practices for Using Open Source Software Safely

Open source software is critical yet potentially dangerous. Here are ways to minimize the risk.
3 of 7

Track and Update Components on Purpose
In the hyper-speed world that is DevOps (or even agile), old code is, at best, a ticking time bomb. At worst, it's the sort of digital 'hack me' sign that criminals love to see in an application.
Statements about how updates should be managed should be part of every open source policy document. According to an article on the AltexSoft blog, 'Any time a bug is found and fixed in an open source project, it's a race against time to ensure you apply the relevant updates to all applications that use libraries or frameworks from those projects.'
One of the keys to keeping components updated is understanding which components are part of the application. A number of tools are available for scanning and enumerating the components in  a project. Coverity Scan, for example, is used within many larger open source projects and enterprises. But regardless of the tool used, it's important the technology support a policy of consistently monitoring and updating named components and their various software dependencies.
(Image: ra2 studio VIA Adobe Stock)

Track and Update Components on Purpose

In the hyper-speed world that is DevOps (or even agile), old code is, at best, a ticking time bomb. At worst, it's the sort of digital "hack me" sign that criminals love to see in an application.

Statements about how updates should be managed should be part of every open source policy document. According to an article on the AltexSoft blog, "Any time a bug is found and fixed in an open source project, it's a race against time to ensure you apply the relevant updates to all applications that use libraries or frameworks from those projects."

One of the keys to keeping components updated is understanding which components are part of the application. A number of tools are available for scanning and enumerating the components in a project. Coverity Scan, for example, is used within many larger open source projects and enterprises. But regardless of the tool used, it's important the technology support a policy of consistently monitoring and updating named components and their various software dependencies.

(Image: ra2 studio VIA Adobe Stock)

3 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
linnovate
50%
50%
linnovate,
User Rank: Apprentice
10/7/2020 | 6:32:04 AM
Additional safety suggestion
It is true, things can quickly get overwhelming in open-source. Ultimately it comes down to trusting the developers, open communication, and having a great teamwork ethic, working collaboratively together. The one thing I would add is knowing who the contributors are. 
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
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-37759
PUBLISHED: 2021-07-31
A Session ID leak in the DEBUG log file in Graylog before 4.1.2 allows attackers to escalate privileges (to the access level of the leaked session ID).
CVE-2021-37760
PUBLISHED: 2021-07-31
A Session ID leak in the audit log in Graylog before 4.1.2 allows attackers to escalate privileges (to the access level of the leaked session ID).
CVE-2020-26564
PUBLISHED: 2021-07-31
ObjectPlanet Opinio before 7.15 allows XXE attacks via three steps: modify a .css file to have <!ENTITY content, create a .xml file for a generic survey template (containing a link to this .css file), and import this .xml file at the survey/admin/folderSurvey.do?action=viewImportSurvey['importFil...
CVE-2020-26565
PUBLISHED: 2021-07-31
ObjectPlanet Opinio before 7.14 allows Expression Language Injection via the admin/permissionList.do from parameter. This can be used to retrieve possibly sensitive serverInfo data.
CVE-2020-26806
PUBLISHED: 2021-07-31
admin/file.do in ObjectPlanet Opinio before 7.15 allows Unrestricted File Upload of executable JSP files, resulting in remote code execution, because filePath can have directory traversal and fileContent can be valid JSP code.