Software vulnerability prioritization using vulnerability description

被引:0
|
作者
Sharma, Ruchi [1 ]
Sibal, Ritu [1 ]
Sabharwal, Sangeeta [1 ]
机构
[1] Netaji Subhas Univ Technol, Dept Comp Engn, Delhi, India
关键词
Prioritization; Convolutional neural network; Vulnerability description; Severity; VRSS;
D O I
10.1007/s13198-020-01021-7
中图分类号
T [工业技术];
学科分类号
08 ;
摘要
Whenever a vulnerability is detected by the testing team, it is described based on its characteristics and a detailed overview of the vulnerability is given by the testing team. Usually, there are certain features or keywords that points towards the possible severity level of a vulnerability. Using these keywords in the vulnerability description, a possible estimation of the severity level of vulnerabilities can be given just by their description. In this paper, we are eliminating the need for generating a severity score for software vulnerabilities by using the description of a vulnerability for their prioritization. This study makes use of word embedding and convolution neural network (CNN). The CNN is trained with sufficient samples vulnerability descriptions from all the categories, so that it can capture discriminative words and features for the categorization task. The proposed system helps to channelize the efforts of the testing team by prioritizing the newly found vulnerabilities in three categories based on previous data. The dataset includes three data samples from three different vendors and two mixed vendor data samples.
引用
收藏
页码:58 / 64
页数:7
相关论文
共 50 条
  • [1] Software vulnerability prioritization using vulnerability description
    Ruchi Sharma
    Ritu Sibal
    Sangeeta Sabharwal
    [J]. International Journal of System Assurance Engineering and Management, 2021, 12 : 58 - 64
  • [2] Learning to Predict Severity of Software Vulnerability Using Only Vulnerability Description
    Han, Zhuobing
    Li, Xiaohong
    Xing, Zhenchang
    Liu, Hongtao
    Feng, Zhiyong
    [J]. 2017 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE AND EVOLUTION (ICSME), 2017, : 125 - 136
  • [3] A novel approach to evaluate software vulnerability prioritization
    Huang, Chien-Cheng
    Lin, Feng-Yu
    Lin, Frank Yeong-Sung
    Sun, Yeali S.
    [J]. JOURNAL OF SYSTEMS AND SOFTWARE, 2013, 86 (11) : 2822 - 2840
  • [4] A Survey on Data-driven Software Vulnerability Assessment and Prioritization
    Le, Triet H. M.
    Chen, Huaming
    Babar, M. Ali
    [J]. ACM COMPUTING SURVEYS, 2023, 55 (05)
  • [5] Automated Software Vulnerability Detection in Statement Level using Vulnerability Reports
    Mim, Rabaya Sultana
    Ahammed, Toukir
    Sakib, Kazi
    [J]. PROCEEDINGS OF 2024 28TH INTERNATION CONFERENCE ON EVALUATION AND ASSESSMENT IN SOFTWARE ENGINEERING, EASE 2024, 2024, : 454 - 455
  • [6] Character-Level Convolutional Neural Network for Predicting Severity of Software Vulnerability from Vulnerability Description
    Nakagawa, Shunta .
    Nagai, Tatsuya
    Kanehara, Hideaki
    Furumoto, Keisuke
    Takita, Makoto
    Shiraishi, Yoshiaki
    Takahashi, Takeshi
    Mohri, Masami
    Takano, Yasuhiro
    Morii, Masakatu
    [J]. IEICE TRANSACTIONS ON INFORMATION AND SYSTEMS, 2019, E102D (09) : 1679 - 1682
  • [7] DeKeDVer: A deep learning-based multi-type software vulnerability classification framework using vulnerability description and source code
    Dong, Yukun
    Tang, Yeer
    Cheng, Xiaotong
    Yang, Yufei
    [J]. INFORMATION AND SOFTWARE TECHNOLOGY, 2023, 163
  • [8] A vulnerability prioritization system using a fuzzy risk analysis approach
    Dondo, Maxwell G.
    [J]. PROCEEDINGS OF THE IFIP TC 11/ 23RD INTERNATIONAL INFORMATION SECURITY CONFERENCE, 2008, : 525 - 539
  • [9] Testing for software vulnerability using environment perturbation
    Du, WL
    Mathur, AP
    [J]. DSN 2000: INTERNATIONAL CONFERENCE ON DEPENDABLE SYSTEMS AND NETWORKS, PROCEEDINGS, 2000, : 603 - 612
  • [10] Vulnerability Scrying Method for Software Vulnerability Discovery Prediction Without a Vulnerability Database
    Rahimi, Sanaz
    Zargham, Mehdi
    [J]. IEEE TRANSACTIONS ON RELIABILITY, 2013, 62 (02) : 395 - 407