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?
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14540
PUBLISHED: 2019-09-15
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
CVE-2019-16332
PUBLISHED: 2019-09-15
In the api-bearer-auth plugin before 20190907 for WordPress, the server parameter is not correctly filtered in the swagger-config.yaml.php file, and it is possible to inject JavaScript code, aka XSS.
CVE-2019-16333
PUBLISHED: 2019-09-15
GetSimple CMS v3.3.15 has Persistent Cross-Site Scripting (XSS) in admin/theme-edit.php.
CVE-2019-16334
PUBLISHED: 2019-09-15
In Bludit v3.9.2, there is a persistent XSS vulnerability in the Categories -> Add New Category -> Name field. NOTE: this may overlap CVE-2017-16636.
CVE-2019-16335
PUBLISHED: 2019-09-15
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.