arXivDaily arXiv每日学术速递 周一至周五更新
北美退伍军人节(Veterans Day),12 日无更新
arXiv 1808.09753cs.SEcs.CR
收藏

易受攻击的开放源代码漏洞:计算那些重要的漏洞

Vulnerable Open Source Dependencies: Counting Those That Matter

Ivan Pashchenko, Henrik Plate, Serena Elisa Ponta, Antonino Sabetta, Fabio Massacci

摘要:

背景技术背景:脆弱的依赖关系是当今开源软件生态系统中的一个已知问题,因为OSS库高度互连,开发人员并不总是更新其依赖关系。目标:在本文中,我们的目标是提出一个精确的方法,结合基于代码的补丁分析与信息构建,测试,更新日期,并从代码库中提取的组,因此,迎合了正确分配开发和审计资源的工业实践的需求。实验方法:为了了解所提出的方法的行业影响,我们考虑了SAP在其软件中使用的200个最流行的OSS Java库。当考虑所有库版本时,我们的分析包括10905个不同的GAV(组,工件,版本)。研究结果:我们发现,受已知漏洞影响的依赖项中约有20%没有部署,因此,它们不会对所分析的库构成危险,因为它们在实践中无法被利用。被分析的库的开发人员能够修复(实际上负责)82%的已部署的易受攻击的依赖项。绝大多数(81%)易受攻击的依赖项可以通过简单地更新到新版本来修复,而我们的样本中有1%的易受攻击的依赖项被停止,因此可能需要昂贵的缓解策略。结论:我们的案例研究表明,正确的计数允许软件开发公司接收有关其库依赖关系的可操作信息,因此,正确分配昂贵的开发和审计资源,这是在扭曲的测量情况下效率低下。

英文摘要:

BACKGROUND: Vulnerable dependencies are a known problem in today's open-source software ecosystems because OSS libraries are highly interconnected and developers do not always update their dependencies. AIMS: In this paper we aim to present a precise methodology, that combines the code-based analysis of patches with information on build, test, update dates, and group extracted from the very code repository, and therefore, caters to the needs of industrial practice for correct allocation of development and audit resources. METHOD: To understand the industrial impact of the proposed methodology, we considered the 200 most popular OSS Java libraries used by SAP in its own software. Our analysis included 10905 distinct GAVs (group, artifact, version) when considering all the library versions. RESULTS: We found that about 20% of the dependencies affected by a known vulnerability are not deployed, and therefore, they do not represent a danger to the analyzed library because they cannot be exploited in practice. Developers of the analyzed libraries are able to fix (and actually responsible for) 82% of the deployed vulnerable dependencies. The vast majority (81%) of vulnerable dependencies may be fixed by simply updating to a new version, while 1% of the vulnerable dependencies in our sample are halted, and therefore, potentially require a costly mitigation strategy. CONCLUSIONS: Our case study shows that the correct counting allows software development companies to receive actionable information about their library dependencies, and therefore, correctly allocate costly development and audit resources, which is spent inefficiently in case of distorted measurements.

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

↑