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.

Security Management

11/1/2017
06:42 PM
Simon Marshall
Simon Marshall
Simon Marshall
50%
50%

Open Source is Getting Safer

Open source is not unsafe by nature, and a new report has numbers to back that up. If your software is unsafe, blame programming, not the license.

How safe is open source software? Critics argue that due to its open nature, the source code is open to engineers but also to hackers. Another accusation is that OSS needs frequent patching, and that response to that requirement can be slow.

Now, there's empirical evidence that the security of OSS has dramatically improved over the last decade. According to a study from Synopsys, a Silicon Valley based firm that specializes in application security testing, secure software development practices that make OSS safer are becoming mainstream.

One big indicator of the continued development of secure software development practices is the apparent level of care taken by teams when using a continuous integration/continuous deployment (CI/CD) methodology. Since January 2016, Synopsys has looked at 4,117 active OSS projects, and about 50% of them use Travis CI, a distributed continuous integration service used to build and test software projects hosted at GitHub.

Synopsys identified more than 1.1 million defects in active OSS projects, leading to the remediation of more than 600,000 defects. This involved the analysis of approximately 760 million lines of open source code across several languages, including C/C++, C#, Java, JavaScript, Ruby, PHP and Python.

The report findings are derived from security data collected over the past decade through Synopsys' own automated static analysis tools, called Coverity and originally created in the Computer Systems Laboratory at Stanford University. In a nutshell, static analysis allows bugs to be identified without ever having to run the software. It applies heuristics to a program's syntax tree, finding defects well in advance of release, limiting the potential impact of flaws.

"Bugs in software will continue to exist while development remains a human endeavor, but the ability fix and respond quickly to vulnerabilities puts OSS at an advantage," Mel Llaguno, open source solution manager for Synopsys Software Integrity Group, told Security Now.

Synopsys said that according to its customers, up to 90% of code shipped in software now consist of OSS, emphasizing just how vital security is during the development process. Also, since it's OSS, bug issues and fixes can be shared among the open source community, speeding troubleshooting.

"Due to the ubiquity of open source and the vital role it plays in virtually all types of software, understanding and managing its risks can no longer be optional," said Andreas Kuehlmann, senior vice president and general manager at Synopsys Software Integrity Group. "The report highlights the progress of some of the most mature and widely used open source projects, and it provides invaluable insights for the broader software community that depends on the integrity of open source."

Related posts:

— Simon Marshall, Technology Journalist, special to Security Now

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17475
PUBLISHED: 2020-08-14
Lack of authentication in the network relays used in MEGVII Koala 2.9.1-c3s allows attackers to grant physical access to anyone by sending packet data to UDP port 5000.
CVE-2020-0255
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-10751. Reason: This candidate is a duplicate of CVE-2020-10751. Notes: All CVE users should reference CVE-2020-10751 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-14353
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-18270. Reason: This candidate is a duplicate of CVE-2017-18270. Notes: All CVE users should reference CVE-2017-18270 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-17464
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2020-17473
PUBLISHED: 2020-08-14
Lack of mutual authentication in ZKTeco FaceDepot 7B 1.0.213 and ZKBiosecurity Server 1.0.0_20190723 allows an attacker to obtain a long-lasting token by impersonating the server.