Impact assessment for vulnerabilities in open-source software libraries

Abstract

Software applications integrate more and more open-source software (OSS) to benefit from code reuse. As a drawback, each vulnerability discovered in bundled OSS potentially affects the application. Upon the disclosure of every new vulnerability, the application vendor has to decide whether it is exploitable in his particular usage context, hence, whether users require an urgent application patch containing a non-vulnerable version of the OSS. Current decision making is mostly based on high-level vulnerability descriptions and expert knowledge, thus, effort intense and error prone. This paper proposes a pragmatic approach to facilitate the impact assessment, describes a proof-of-concept for Java, and examines one example vulnerability as case study. The approach is independent from specific kinds of vulnerabilities or programming languages and can deliver immediate results.

Cited by in corpus (7)

• Do Developers Update Their Library Dependencies? An Empirical Study on the Impact of Security Advisories on Library Migration
• Beyond Metadata: Code-centric and Usage-based Analysis of Known Vulnerabilities in Open-source Software
• An Empirical Analysis of Vulnerabilities in Python Packages for Web Applications
• Vulnerable Open Source Dependencies: Counting Those That Matter
• VulnEx: Exploring Open-Source Software Vulnerabilities in Large Development Organizations to Understand Risk Exposure
• SpellBound: Defending Against Package Typosquatting
• Automated Mapping of Vulnerability Advisories onto their Fix Commits in Open Source Repositories