Predicting Likely-Vulnerable Code Changes: Machine Learning-based Vulnerability Protections for Android Open Source Project
Not on the map. Why?
Abstract (arXiv)
This paper presents a framework that selectively triggers security reviews for incoming source code changes. Functioning as a review bot within a code review service, the framework can automatically request additional security reviews at pre-submit time before the code changes are submitted to a source code repository. Because performing such secure code reviews add cost, the framework employs a classifier trained to identify code changes with a high likelihood of vulnerabilities. The online classifier leverages various types of input features to analyze the review patterns, track the software engineering process, and mine specific text patterns within given code changes. The classifier and its features are meticulously chosen and optimized using data from the submitted code changes and reported vulnerabilities in Android Open Source Project (AOSP). The evaluation results demonstrate that our Vulnerability Prevention (VP) framework identifies approximately 80% of the vulnerability-inducing code changes in the dataset with a precision ratio of around 98% and a false positive rate of around 1.7%. We discuss the implications of deploying the VP framework in multi-project settings and future directions for Android security research. This paper explores and validates our approach to code change-granularity vulnerability prediction, offering a preventive technique for software security by preemptively detecting vulnerable code changes before submission.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 5 of its 45 references that are in the map. First posted on arXiv 26 May 2024.
Builds on
5 of 45 references.
References · 5
- 2022Taxonomy of Attacks on Open-Source Software Supply Chainscited by 58
- 2021An Empirical Study of OSS-Fuzz Bugscited by 7
- 2020A Comprehensive Study of Bloated Dependencies in the Maven Ecosystemcited by 5
- 2017An Empirical Study on Android-related Vulnerabilitiescited by 2
- 2020An Empirical Study of Android Security Bulletins in Different Vendorscited by 2
Built on by
Not cited yet.