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
Oldest First  |  Newest First  |  Threaded View
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?
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.
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: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.
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). 
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. 
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
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-2020-27184
PUBLISHED: 2021-05-14
The NPort IA5000A Series devices use Telnet as one of the network device management services. Telnet does not support the encryption of client-server communications, making it vulnerable to Man-in-the-Middle attacks.
CVE-2020-27185
PUBLISHED: 2021-05-14
Cleartext transmission of sensitive information via Moxa Service in NPort IA5000A series serial devices. Successfully exploiting the vulnerability could enable attackers to read authentication data, device configuration, and other sensitive data transmitted over Moxa Service.
CVE-2021-32613
PUBLISHED: 2021-05-14
In radare2 through 5.3.0 there is a double free vulnerability in the pyc parse via a crafted file which can lead to DoS.
CVE-2021-24192
PUBLISHED: 2021-05-14
Low privileged users can use the AJAX action 'cp_plugins_do_button_job_later_callback' in the Tree Sitemap WordPress plugin before 2.9, to install any plugin (including a specific version) from the WordPress repository, as well as activate arbitrary plugin from then blog, which helps attackers insta...
CVE-2021-24193
PUBLISHED: 2021-05-14
Low privileged users can use the AJAX action 'cp_plugins_do_button_job_later_callback' in the Visitor Traffic Real Time Statistics WordPress plugin before 2.12, to install any plugin (including a specific version) from the WordPress repository, as well as activate arbitrary plugin from then blog, wh...