arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2104.04385cs.SE
收藏

安全测试中的内存错误检测

Memory Error Detection in Security Testing

Nasif Imtiaz, Laurie Williams

摘要:

我们研究了10个使用静态分析安全测试工具的C/C++项目。我们分析了该工具生成的历史扫描报告,并研究了与内存相关的警报出现的频率。我们还研究了开发人员对这些警报的后续操作。我们还查看了在研究时间轴内为这些项目发布的CVE,并调查其中有多少与记忆相关。此外,对于这个项目之一,Linux,我们调查,如果所涉及的漏洞在CVE被确定的研究安全工具时,他们第一次被引入到代码中。我们发现在静态分析安全测试期间经常检测到与内存相关的警报。然而,根据项目开发人员监控工具警报的积极程度,这些错误可能需要数年时间才能修复。对于10个研究项目,我们发现记忆警报修复前的平均寿命为77天。我们还发现,大约40%的研究C/C++项目的已发布的CVE与内存有关。与非内存CVE相比,这些内存CVE具有更高的CVSS严重性等级和公开漏洞利用脚本的可能性。我们还发现,在静态分析安全测试期间,只有2.5%的Linux CVE可能被检测到。

英文摘要:

We study 10 C/C++ projects that have been using a static analysis security testing tool. We analyze the historical scan reports generated by the tool and study how frequently memory-related alerts appeared. We also studied the subsequent developer action on those alerts. We also look at the CVEs published for these projects within the study timeline and investigate how many of them are memory related. Moreover, for one of this project, Linux, we investigate if the involved flaws in the CVE were identified by the studied security tool when they were first introduced in the code. We found memory related alerts to be frequently detected during static analysis security testing. However, based on how actively the project developers are monitoring the tool alerts, these errors can take years to get fixed. For the ten studied projects, we found a median lifespan of 77 days before memory alerts get fixed. We also find that around 40% of the published CVEs for the studied C/C++ projects are related to memory. These memory CVEs have higher CVSS severity ratings and likelihood of having an exploit script public than non-memory CVEs. We also found only 2.5% Linux CVEs were possibly detected during static analysis security testing.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑