2019
DOI: 10.18293/seke2019-183
|View full text |Cite
|
Sign up to set email alerts
|

Detecting Security Vulnerabilities using Clone Detection and Community Knowledge

Abstract: Faced with the severe financial and reputation implications associated with data breaches, enterprises now recognize security as a top concern for software analysis tools. While software engineers are typically not equipped with the required expertise to identify vulnerabilities in code, community knowledge in the form of publicly available vulnerability databases could come to their rescue. For example, the Common Vulnerabilities and Exposures Database (CVE) contains data about already reported weaknesses. Ho… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
2
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 20 publications
0
2
0
Order By: Relevance
“…Typically, software engineers are not qualified to spot vulnerabilities in code, community knowledge, such as publicly accessible vulnerability databases, can help (Viertel et al, 2019). Literature shows that there are three sources of vulnerability data; the first is public databases, such as CVE, NVD, or snyk.io; the second is software producers' databases, such as Microsoft security bulletins; the third is specialized databases (Massacci and Nguyen, 2010).…”
Section: Intrinsic Trust Factormentioning
confidence: 99%
“…Typically, software engineers are not qualified to spot vulnerabilities in code, community knowledge, such as publicly accessible vulnerability databases, can help (Viertel et al, 2019). Literature shows that there are three sources of vulnerability data; the first is public databases, such as CVE, NVD, or snyk.io; the second is software producers' databases, such as Microsoft security bulletins; the third is specialized databases (Massacci and Nguyen, 2010).…”
Section: Intrinsic Trust Factormentioning
confidence: 99%
“…Methods based on text [4] and lexical [5] approaches have the following limitations. They do not use information about the general structure of the code, which negatively affects the classification accuracy, and are also not effective for detecting Type-4 semantic clones.…”
Section: Introductionmentioning
confidence: 99%
“…Source code clone research is a very active field which includes, among other things, research on technologies, algorithms and tools for clone detection (e.g., [39]), studies on the harmfulness of clones (e.g., [40]), studies of the relation between clones and vulnerabilities (e.g., [41]), technologies, algorithms and tools for code clone refactoring (e.g., [42]). This section is not meant to discuss all aspects of research on source code clone;…”
Section: Related Work On Overlapping Information In Clone Detection Rmentioning
confidence: 99%