2021
DOI: 10.1109/tifs.2020.3047756
|View full text |Cite
|
Sign up to set email alerts
|

VulDetector: Detecting Vulnerabilities Using Weighted Feature Graph Comparison

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2021
2021
2025
2025

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 35 publications
(11 citation statements)
references
References 29 publications
0
8
0
Order By: Relevance
“…e proposed model achieves an AUC value of 97.17 on OpenSSL and Linux on a data set of 876 samples. To address the problems of high false positives and poor performance when analyzing large programs, Cui et al propose to use the weighted feature graph (WFG), a small but semantically rich graph to characterize functions and build a static VulDetector [19]. VulDetector firstly seeks vulnerability-sensitive keywords to reduce the size of the graph without compromising securityrelated semantics.…”
Section: Rule-basedmentioning
confidence: 99%
“…e proposed model achieves an AUC value of 97.17 on OpenSSL and Linux on a data set of 876 samples. To address the problems of high false positives and poor performance when analyzing large programs, Cui et al propose to use the weighted feature graph (WFG), a small but semantically rich graph to characterize functions and build a static VulDetector [19]. VulDetector firstly seeks vulnerability-sensitive keywords to reduce the size of the graph without compromising securityrelated semantics.…”
Section: Rule-basedmentioning
confidence: 99%
“…The introduction of GNNs for modelling vulnerabilities was originally inspired by the vulnerability discovery approach proposed by Yamaguchi et al [60] using Code Property Graphs, a type of program graph incorporating program dependency edges [26,40], control flow edges, and the abstract syntax tree of the program, which provide an additional source of information to learn from [14]. Hence, the performance improvements using GNNs can primarily be attributed to leveraging the domain knowledge that lines of source code within a program have specific relationships to other lines; i.e., training using both semantic and syntactical information, rather than only syntactical information.…”
Section: Software Vulnerability Detection With Gnnmentioning
confidence: 99%
“…[45], [49], [50], [73], by matching vulnerability signatures [42], [47] and by matching both vulnerability and patch signatures [35], [66], [67]. Similar to those patch analysis works, the mappings between CVEs and their patches in these works are mostly identified by manual efforts [58], [59], [60], [66] and heuristics rules [45], [49], [50], [65], [70], or directly taken from security advisories that establish the mapping between CVEs and patches for specific projects [42], [47], [67].…”
Section: Related Workmentioning
confidence: 99%
“…To this end, tremendous efforts have been made to mitigate security risks in OSS vulnerabilities, ranging from detecting vulnerabilities in open source software via learning vulnerability features [45], [49], [50], [73], or matching vulnerability and/or patch signatures [35], [42], [47], [66], [67], to patching vulnerabilities in open source software [39], [52], [54], [69], or analyzing software composition for determining whether open source vulnerabilities are reachable through call paths in applications [58], [59], [60], [65]. In particular, vulnerability databases play a significant role in these efforts by providing valuable data (e.g., description, affected software and versions, and patches) for various vulnerability analysis tasks.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation