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
50%
50%

6 Best Practices for Using Open Source Software Safely

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

It's no longer a question of whether enterprise software is developed using open source code, but just how much open source code makes up each application. And as DevOps becomes the default development discipline for more organizations, the pressure to reach out and grab reusable modules and libraries is almost guaranteed to make open source code a greater percentage of enterprise software.

Even with commercial software, questions about third-party risk and supply chain security loom large. When those questions extend to open source software, they can become absolutely overwhelming.

Research bears that out. In reviewing enterprise codebases submitted for audit, Synopsis found 70% of the code was open source. While not in any way an indictment in and of itself, 73% of codebases they found had at least one licensing issue and 82% included 4-year-old code. Combined, the security and reliability of applications containing open source software becomes a legitimate concern.

As with so many facets of cybersecurity, attention to detail carries a great deal of weight when it comes to keeping open source containing projects safe and secure. What else do you need to know? Dark Reading combed the Internet and reviewed numerous conversations we've had in recent months to put together this collection of best practices. Let us know whether you have any of your own in the Comments section, below.

(Image: duncanandison VIA Adobe Stock)

 

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio
 

Recommended Reading:

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest 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. 
Eloisetacos
50%
50%
Eloisetacos,
User Rank: Apprentice
10/13/2020 | 6:03:00 AM
Attention to detail
Thank you for this interesting article. As you say, I agree with bringing his attention to detail carries a great deal of weight when it comes to keeping open source containing projects safe and secure.
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29378
PUBLISHED: 2020-11-29
An issue was discovered on V-SOL V1600D V2.03.69 and V2.03.57, V1600D4L V1.01.49, V1600D-MINI V1.01.48, V1600G1 V2.0.7 and V1.9.7, and V1600G2 V1.1.4 OLT devices. It is possible to elevate the privilege of a CLI user (to full administrative access) by using the password [email protected]#y$z%x6x7q8c9z) for the e...
CVE-2020-29379
PUBLISHED: 2020-11-29
An issue was discovered on V-SOL V1600D4L V1.01.49 and V1600D-MINI V1.01.48 OLT devices. During the process of updating the firmware, the update script starts a telnetd -l /bin/sh process that does not require authentication for TELNET access.
CVE-2020-29380
PUBLISHED: 2020-11-29
An issue was discovered on V-SOL V1600D V2.03.69 and V2.03.57, V1600D4L V1.01.49, V1600D-MINI V1.01.48, V1600G1 V2.0.7 and V1.9.7, and V1600G2 V1.1.4 OLT devices. TELNET is offered by default but SSH is not always available. An attacker can intercept passwords sent in cleartext and conduct a man-in-...
CVE-2020-29381
PUBLISHED: 2020-11-29
An issue was discovered on V-SOL V1600D V2.03.69 and V2.03.57, V1600D4L V1.01.49, V1600D-MINI V1.01.48, V1600G1 V2.0.7 and V1.9.7, and V1600G2 V1.1.4 OLT devices. Command injection can occur in "upload tftp syslog" and "upload tftp configuration" in the CLI via a crafted filename...
CVE-2020-29382
PUBLISHED: 2020-11-29
An issue was discovered on V-SOL V1600D V2.03.69 and V2.03.57, V1600G1 V2.0.7 and V1.9.7, and V1600G2 V1.1.4 OLT devices. A hardcoded RSA private key (specific to V1600D, V1600G1, and V1600G2) is contained in the firmware images.