TL;DR
This study investigates the correlation between code and architectural smells and software vulnerabilities, finding certain code smells significantly associated with vulnerabilities across multiple systems, which can aid in vulnerability prediction.
Contribution
It identifies specific code smells that are statistically linked to vulnerabilities, providing insights for improving vulnerability prediction models.
Findings
Certain code smells are significantly associated with vulnerabilities.
No significant relationship found between architectural smells and vulnerabilities.
Vulnerable classes tend to have specific code smells more frequently.
Abstract
Context: Security is vital to software developed for commercial or personal use. Although more organizations are realizing the importance of applying secure coding practices, in many of them, security concerns are not known or addressed until a security failure occurs. The root cause of security failures is vulnerable code. While metrics have been used to predict software vulnerabilities, we explore the relationship between code and architectural smells with security weaknesses. As smells are surface indicators of a deeper problem in software, determining the relationship between smells and software vulnerabilities can play a significant role in vulnerability prediction models. Objective: This study explores the relationship between smells and software vulnerabilities to identify the smells. Method: We extracted the class, method, file, and package level smells for three systems: Apache…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
