theDocumentId => 1316738 Open Source v. Closed Source: What's More Secure?

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

Open Source v. Closed Source: What's More Secure?

0%
100%

In the wake of Shellshock and Heartbleed, has the glow of open-source application security dimmed?

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
10/21/2014 | 11:07:40 AM
Re: Devil's Advocate
Agreed, sometimes when something is implemented that cannot increase security posture you need to go back to the framework and make changes to the baseline. This may be off topic from Open Source vs Closed Source, but DoS is the same way. Its still very prevalent due to the way hardware handles packets. A needed functionality, so changes need to be made to the overall hardware handling. However, I do think that more hands involved in the rearchitecture would be optimal. 
Lucamp
50%
50%
Lucamp,
User Rank: Strategist
10/21/2014 | 5:29:54 AM
Open source
From my persective, open source is more secure and more people work on it that in close code. However, the types of vulnerabilites that open source is exposed is different that in close code. Also the quality of open source projeects is higher that in close code from my experience (Two Big Companies). 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:46:59 PM
Re: Devil's Advocate
Good point. That also depends of the architecture of the system, you can not make Java any more secure regardless of how many developers you put on it. A new way of thinking and architecture is needed for that.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:44:47 PM
Agree with the video
 

I think video is taking right approach tough, no need to differentiate open source from closed source when it comes to security, both will have vulnerabilities and they requires us to do ongoing monitoring and analysis to catch those vulnerabilities before they heard us.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:42:17 PM
Open source
Open source may reveal more information in its structure but at the same time it may also be an environment that vulnerabilities are found and mitigated early enough since more than one set of eyes are looking at it.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
10/20/2014 | 11:16:26 AM
Devil's Advocate
I agree very much with this ideology of closed versus open source. But to be the devil's advocate, wouldn't the same reason provided "more people being able to see the source code" also provide for a more adept security model. In theory, the more eyes that look at the code the greater the exposure to expanding on that code beneficially. This includes not only security but app development. Linux and Linux derivatives are very much based on this methodology. What reasoning then is it assumed that more exposure to the code will result in a detrimental outcome over a beneficial one?
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-32686
PUBLISHED: 2021-07-23
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In PJSIP before version 2.11.1, there are a couple of issues found in the SSL socket. First, a race condition between callback and ...
CVE-2021-32783
PUBLISHED: 2021-07-23
Contour is a Kubernetes ingress controller using Envoy proxy. In Contour before version 1.17.1 a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy rem...
CVE-2021-3169
PUBLISHED: 2021-07-23
An issue in Jumpserver 2.6.2 and below allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.
CVE-2020-20741
PUBLISHED: 2021-07-23
Incorrect Access Control in Beckhoff Automation GmbH & Co. KG CX9020 with firmware version CX9020_CB3011_WEC7_HPS_v602_TC31_B4016.6 allows remote attackers to bypass authentication via the "CE Remote Display Tool" as it does not close the incoming connection on the Windows CE side if t...
CVE-2021-25808
PUBLISHED: 2021-07-23
A code injection vulnerability in backup/plugin.php of Bludit 3.13.1 allows attackers to execute arbitrary code via a crafted ZIP file.