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
Re-innovating Static Analysis: 4 Steps
Newest First  |  Oldest First  |  Threaded View
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
12/15/2015 | 2:33:16 PM
Re: The *term* static analysis should die
Jeff... that's not the case.  I think there are ways (we have been exploring) to correlate and bring disparate results together; as well as the context of various security testing activiites -- see ASTAM.  So.. we have already explored new ways to bring results together.. I think we are moving in the right direction.  Lots of exciting things to come... Thanks for reading...
planetlevel
50%
50%
planetlevel,
User Rank: Author
12/15/2015 | 12:26:30 PM
The *term* static analysis should die
Hi Kevin - nice article.  Just wanted to check if you thought it was me suggesting static analysis is dead -- which I don't.  I have written that the *term* static analysis should die.  At least for security.  I think I've been clear that I use and trust static analysis for many types of code quality analysis.

http://www.contrastsecurity.com/blog/why-its-time-for-the-terms-static-analysis-and-dynamic-analysis-to-die

The basic idea is that it's the information -- the context -- available to the tool that matters, not the fact that it happens to be static, dynamic, interactive, runtime, or whatever.  We should be talking about whether a tool has access to accurate data flow, backend connections, http requests/responses, libraries/frameworks, etc...  That's what tools need to start getting accurate.

And I want to be clear. This isn't about correlating the results of single-approach tools. My experience is that it's very difficult to accurately correlate.  And even if you do, you lose the "sweet spots" that were only found by one tool and so didn't correlate with anything.  I'm talking about merging the analysis techniques themselves into a single tool - so that the analysis engine itself can use a broad range of contextual information when identifying vulnerabilities.

Static analysis is a key security technology. But in my view needs the information from other security analysis approaches closely integrated during analysis.  I look forward to seeing the results of the STAMP.

 

 

 
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
12/14/2015 | 1:13:09 PM
Re: nice post
Thanks for the support.  Much appreciated.. 
Poissonpraveen
50%
50%
Poissonpraveen,
User Rank: Apprentice
12/11/2015 | 8:03:51 AM
nice post
nice post and good peice of information and keep it bro...


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
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-2020-10696
PUBLISHED: 2020-03-31
A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.
CVE-2020-5344
PUBLISHED: 2020-03-31
Dell EMC iDRAC7, iDRAC8 and iDRAC9 versions prior to 2.65.65.65, 2.70.70.70, 4.00.00.00 contain a stack-based buffer overflow vulnerability. An unauthenticated remote attacker may exploit this vulnerability to crash the affected process or execute arbitrary code on the system by sending specially cr...
CVE-2020-5292
PUBLISHED: 2020-03-31
Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and admini...
CVE-2020-7009
PUBLISHED: 2020-03-31
Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
CVE-2019-13495
PUBLISHED: 2020-03-31
In firmware version 4.50 of Zyxel XGS2210-52HP, multiple stored cross-site scripting (XSS) issues allows remote authenticated users to inject arbitrary web script via an rpSys.html Name or Location field.