Cited by 34Software Testing and Debugging TechniquesSoftware Engineering ResearchSecurity and Verification in Computing

A Case Study of LLM for Automated Vulnerability Repair: Assessing Impact of Reasoning and Patch Validation Feedback

Open access
Kulsum, Ummay, Zhu, Haotian, Xu, Bowen, d'Amorim, Marcelo·2024·Proceedings of the 1st ACM International Conference on AI-Powered Software

Abstract

Recent work in automated program repair (APR) proposes the use of reasoning and patch validation feedback to reduce the semantic gap between the LLMs and the code under analysis. The idea has been shown to perform well for general APR, but its effectiveness in other particular contexts remains underexplored. In this work, we assess the impact of reasoning and patch validation feedback to LLMs in the context of vulnerability repair, an important and challenging task in security. To support the evaluation, we present VRpilot, an LLM-based vulnerability repair technique based on reasoning and patch validation feedback. VRpilot (1) uses a chain-of-thought prompt to reason about a vulnerability prior to generating patch candidates and (2) iteratively refines prompts according to the output of external tools (e.g., compiler, code sanitizers, test suite, etc.) on previously generated patches. To evaluate performance, we compare VRpilot against the state-of-the-art vulnerability repair techniques for C and Java using public datasets from the literature. Our results show that VRpilot generates, on average, 14% and 7.6% more correct patches than the baseline techniques on C and Java, respectively. We show, through an ablation study, that reasoning and patch validation feedback are critical. We report several lessons from this study and potential directions for advancing LLM-empowered vulnerability repair.

Integrity signals

Registry

Crossref · 10.1145/3664646.3664770

Cites

2 of 2 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • VRpilot is based on reasoning and patch validation feedback, using a chain-of-thought prompt to reason about a vulnerability before generating patch candidates and iteratively refining prompts based on feedback from external tools.

    “Similarly, VRpilot (Kulsum et al/ 2024) is based on reasoning and patch validation feedback. The method uses a chain-of-thought prompt to reason about a vulnerability before generating patch candidates and iteratively refines the prompts based on feedback from external tools on previously generated”

    From When LLMs meet cybersecurity: a systematic literature review (2025) · cites this paper as Kulsum et al/ 2024

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Kulsum, U., Zhu, H., Xu, B., & d'Amorim, M.
Affiliations
  • North Carolina State University (US)
  • Singapore Management University (SG)
  • North Carolina State University, Raleigh, USA
Venue
Proceedings of the 1st ACM International Conference on AI-Powered Software
Publisher
ACM
Published
2024-07-10
Pages
103-111
OpenAlex
W4400484609
Cited by
34
References
2
Citations by year
2026: 18 · 2025: 15 · 2024: 1
FWCI
9.26
Type
conference paper
Language
en
Open access
Locations
  • ACM International Conference on AI-Powered Software (AIware) (publishedVersion)
  • arXiv (Cornell University) (submittedVersion, cc-by)
  • arXiv (Cornell University) (cc-by)
Funders
National Science Foundation (2026928)
Topics
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Artificial Intelligence › Security and Verification in Computing
Keywords
automated vulnerability repair, large language models, chain-of-thought prompting, prompt refinement, C programs, Java programs, software security

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review