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.


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
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-42258
PUBLISHED: 2021-10-22
BQE BillQuick Web Suite 2018 through 2021 before 22.0.9.1 allows SQL injection for unauthenticated remote code execution, as exploited in the wild in October 2021 for ransomware installation. SQL injection can, for example, use the txtID (aka username) parameter. Successful exploitation can include ...
CVE-2020-28968
PUBLISHED: 2021-10-22
Draytek VigorAP 1000C contains a stored cross-site scripting (XSS) vulnerability in the RADIUS Setting - RADIUS Server Configuration module. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the username input field.
CVE-2020-28969
PUBLISHED: 2021-10-22
Aplioxio PDF ShapingUp 5.0.0.139 contains a buffer overflow which allows attackers to cause a denial of service (DoS) via a crafted PDF file.
CVE-2020-36485
PUBLISHED: 2021-10-22
Portable Ltd Playable v9.18 was discovered to contain an arbitrary file upload vulnerability in the filename parameter of the upload module. This vulnerability allows attackers to execute arbitrary code via a crafted JPEG file.
CVE-2020-36486
PUBLISHED: 2021-10-22
Swift File Transfer Mobile v1.1.2 and below was discovered to contain a cross-site scripting (XSS) vulnerability via the 'path' parameter of the 'list' and 'download' exception-handling.