arXiv:2611.18568v1 Announce Type: new Abstract: Context: Security vulnerabilities in OSS can have severe consequences. OSS project participants widely use peer code review to improve quality and prevent security flaws. However, despite mandatory reviews, OSS projects still contain vulnerabilities, highlighting the need to evaluate code review effectiveness for security. Objectives: This SLR synthesizes evidence on vulnerability types identified or missed, security practices, tool support, reviewer challenges, and factors that improve detection. Method: Searches of five digital libraries yielded 1,067 studies, of which 20 were included. Vulnerabilities were categorized using the Common Weakness Enumeration (CWE) framework. Results: Peer code reviews effectively detect localized, well-known vulnerabilities (e.g., buffer overruns, race conditions, crashes, XSS) but often miss subtle, complex, context-dependent issues (e.g., input validation weaknesses, access control weaknesses, resource lifecycle weaknesses). Effective security practices are associated with reviewer expertise, code familiarity, frequent small changes, and organizational support. Security analysis tools, especially Static Application Security Testing (SAST) tools, reduce reviewer effort and improve detection but cannot replace human judgment. Reviewers continue to face limitations in security knowledge, experience, time, and understanding of complex systems. Effectiveness improves through security training, domain expertise, contextual familiarity, formalized review processes, and supportive review environments. Conclusion: Peer code review contributes to OSS security but is insufficient on its own. Improving effectiveness requires structured review processes and checklists, security training, organizational incentives, and lightweight automated tool support to help reviewers detect subtle vulnerabilities while reinforcing secure development practices.
Continue to arXiv Software Engineering →You are being forwarded in 6s — stay on this page