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
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
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
[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
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
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-4221
PUBLISHED: 2022-12-01
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Asus NAS-M25 allows an unauthenticated attacker to inject arbitrary OS commands via unsanitized cookie values.This issue affects NAS-M25: through 1.0.1.7.
CVE-2022-45050
PUBLISHED: 2022-12-01
A reflected XSS vulnerability has been found in Axiell Iguana CMS, allowing an attacker to execute code in a victim's browser. The title parameter on the twitter.php endpoint does not properly neutralise user input, resulting in the vulnerability.
CVE-2022-4246
PUBLISHED: 2022-12-01
A vulnerability classified as problematic has been found in Kakao PotPlayer. This affects an unknown part of the component MID File Handler. The manipulation leads to denial of service. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The ...
CVE-2022-4247
PUBLISHED: 2022-12-01
A vulnerability classified as critical was found in Movie Ticket Booking System. This vulnerability affects unknown code of the file booking.php. The manipulation of the argument id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be ...
CVE-2022-4248
PUBLISHED: 2022-12-01
A vulnerability, which was classified as critical, has been found in Movie Ticket Booking System. This issue affects some unknown processing of the file editBooking.php. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed t...