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?
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9349
PUBLISHED: 2020-04-02
The CACAGOO Cloud Storage Intelligent Camera TV-288ZD-2MP with firmware 3.4.2.0919 allows access to the RTSP service without a password.
CVE-2020-11100
PUBLISHED: 2020-04-02
In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution.
CVE-2020-11450
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 exposes the JVM configuration, CPU architecture, installation folder, and other information through the URL /MicroStrategyWS/happyaxis.jsp. An attacker could use this vulnerability to learn more about the environment the application is running in.
CVE-2020-11451
PUBLISHED: 2020-04-02
The Upload Visualization plugin in the Microstrategy Web 10.4 admin panel allows an administrator to upload a ZIP archive containing files with arbitrary extensions and data. (This is also exploitable via SSRF.)
CVE-2020-11454
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 is vulnerable to Stored XSS in the HTML Container and Insert Text features in the window, allowing for the creation of a new dashboard. In order to exploit this vulnerability, a user needs to get access to a shared dashboard or have the ability to create a dashboard on the app...