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.

Comments
Risky Business: Why Monitoring Vulnerability Data Is Never Enough
Newest First  |  Oldest First  |  Threaded View
dferguson_usa
50%
50%
dferguson_usa,
User Rank: Apprentice
3/20/2015 | 8:14:04 PM
Static analysis vs. vulnerable components database
Veracode offers a static analysis solution similar to Coverity, but it works on the compiled code and not the source code.  Anyway I'm not sure doing static analysis on your 3rd party libraries/open source components is practical.  You may end up with a much bigger project than you want.  And these tools can have false negatives like already mentioned.  Probably more effective is to use an automated solution that can figure out what components are present in your software and then checks a database to flag known vulnerable components.  OWASP has a tool called Dependency Check that is designed to do this, and there's no cost.  I haven't used it myself yet though.
xmarksthespot
50%
50%
xmarksthespot,
User Rank: Strategist
3/20/2015 | 4:25:34 AM
Re: What abput Coverity?
The way I learned so much in penetration testing and web development, is from open source. I use Kali and Ubuntu along with the multitude of open source within it. I *love* it!

I don't see reliable evidence that closed source is more vulnerable than open source, or vice versa. In my mind it would have to be examined on a case by case basis on the technologies available. There are many factors involved in analyzing the security level of a package. You see critical vulnerabilities reported in both types of software, frequently. That's not the complete picture in terms of the security. Just because a hole isn't found doesn't mean there isn't a hole there.

Some open source software have strong communities which react quickly when vulnerabilities are reported. Others are slower. Same goes for commercial software. Personally, I'd be concerned about fast patches get applied to reported vulnerabilities If reported vulnerabilities are not patched in a timely manner, I would be suspect of the product, open or closed source.

It seems prudent that a large corporation relying heavily on a particular project would give it a look. I'm sure that in many cases they are already doing that. Also, I think it would be most important to perform periodic and structured security audits on open source security mechanisms such as OpenSSL.
bill@blackduck
50%
50%
[email protected],
User Rank: Author
3/19/2015 | 9:31:16 PM
Re: What abput Coverity?

I agree, running static code analysis tools such as Coverity are certainly best practice for finding defects and vulnerabilities in both open source and proprietary code. I believe that Coverity even offers a free service for open source projects to scan their code. Unfortunately, not all open source projects do this. In addition, not all vulnerabilities are caught by these tools — many are discovered by security researchers analyzing the code directly. Thus, it still makes sense to have an accounting of what open source software you are using and what known vulnerabilities have been reported against those projects and versions.

Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Ninja
3/19/2015 | 7:17:03 PM
What abput Coverity?
i don't know what it costs but Coverity will perform a static check on all code sent to it for a fee. It looks for security vulnerability and poor coding practices and gives you a report. This may not be what's needed to maintain your open source code but it seems to me some kind of periodic check by an outside third party would be a good way to go.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/10/2020
Zscaler to Buy Cloudneeti
Dark Reading Staff 4/9/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Yes, I do have virus protection on my system, now what?
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
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18375
PUBLISHED: 2020-04-10
The ASG and ProxySG management consoles are susceptible to a session hijacking vulnerability. A remote attacker, with access to the appliance management interface, can hijack the session of a currently logged-in user and access the management console.
CVE-2019-18376
PUBLISHED: 2020-04-10
A CSRF token disclosure vulnerability allows a remote attacker, with access to an authenticated Management Center (MC) user's web browser history or a network device that intercepts/logs traffic to MC, to obtain CSRF tokens and use them to perform CSRF attacks against MC.
CVE-2019-7305
PUBLISHED: 2020-04-10
Information Exposure vulnerability in eXtplorer makes the /usr/ and /etc/extplorer/ system directories world-accessible over HTTP. Introduced in the Makefile patch file debian/patches/debian-changes-2.1.0b6+dfsg-1 or debian/patches/adds-a-makefile.patch, this can lead to data leakage, information di...
CVE-2020-8832
PUBLISHED: 2020-04-10
The fix for the Linux kernel in Ubuntu 18.04 LTS for CVE-2019-14615 ("The Linux kernel did not properly clear data structures on context switches for certain Intel graphics processors.") was discovered to be incomplete, meaning that in versions of the kernel before 4.15.0-91.92, an attacke...
CVE-2020-1633
PUBLISHED: 2020-04-09
Due to a new NDP proxy feature for EVPN leaf nodes introduced in Junos OS 17.4, crafted NDPv6 packets could transit a Junos device configured as a Broadband Network Gateway (BNG) and reach the EVPN leaf node, causing a stale MAC address entry. This could cause legitimate traffic to be discarded, lea...