Back to AI News
arxiv

A.S.E 2.0: How Repository Context Impacts the Security of LLM-Generated Code

This paper introduces CASE-Bench, a benchmark of 145 repository-level tasks derived from real CVEs across 51 projects, to study how repository context affects the security of LLM-generated code. Experiments with 13 context construction methodshol and six LLMs show that functionality-oriented context improves functional pass rates more than secure pass rates, and that withholding safeguards or inserting insecure examples significantly increases exploitable code. Coding agents observe relevant safeguards in only 27-36% of trajectories, highlighting the need for security-aware context construction.

AI Brief

Provides concrete, recent evidence and a new benchmark on a critical but understudied aspect of LLM code security, offering actionable insights for developers and researchers.

arXiv:2611.06294v1 Announce Type: cross Abstract: Large language model (LLM) coding assistants and agents construct a repository context before generating code. For security-sensitive code, this context decides whether the model sees the project's safeguards (e.g., authorization checks) or insecure code to imitate. However, context construction is designed almost exclusively for functional correctness, and secure-code benchmarks treat the context as fixed, so how repository context affects the security of generated code remains unclear. We construct CASE-Bench, a benchmark of 145 repository-level tasks from real CVEs in 51 projects. Each task runs in Docker, has functional tests and a proof-of-concept exploit validated in both directions, and is annotated with the repository code that enforces or undermines its security. Using CASE-Bench, we compare 13 context construction methods and six controls with six LLMs, edit single context elements, and analyze coding-agent trajectories. We find that (1) functionality-oriented context raises the functional pass rate by up to 8.2 percentage points (pp) but the secure pass rate by at most 3.7 pp, (2) withholding a safeguard lowers the secure pass rate by up to 8.1 pp, while one inserted insecure exemplar raises correct-but-exploitable code by 6.3 pp, and (3) coding agents observe the relevant safeguard in only 27-36% of trajectories. These findings inform security-aware context construction and secure-code evaluation.
Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!