Pith. sign in

REVIEW 4 cited by

CASTLE: Benchmarking Dataset for Static Code Analyzers and LLMs towards CWE Detection

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 2503.09433 v2 pith:RGHNX25V submitted 2025-03-12 cs.CR cs.AIcs.SE

classification cs.CRcs.AIcs.SE
keywords codecastledatasetllmsstaticvulnerabilitiesanalysisformal
verification ladder T0 review T1 audit T2 compute T3 formal
0 comments
read the original abstract

Identifying vulnerabilities in source code is crucial, especially in critical software components. Existing methods such as static analysis, dynamic analysis, formal verification, and recently Large Language Models are widely used to detect security flaws. This paper introduces CASTLE (CWE Automated Security Testing and Low-Level Evaluation), a benchmarking framework for evaluating the vulnerability detection capabilities of different methods. We assess 13 static analysis tools, 10 LLMs, and 2 formal verification tools using a hand-crafted dataset of 250 micro-benchmark programs covering 25 common CWEs. We propose the CASTLE Score, a novel evaluation metric to ensure fair comparison. Our results reveal key differences: ESBMC (a formal verification tool) minimizes false positives but struggles with vulnerabilities beyond model checking, such as weak cryptography or SQL injection. Static analyzers suffer from high false positives, increasing manual validation efforts for developers. LLMs perform exceptionally well in the CASTLE dataset when identifying vulnerabilities in small code snippets. However, their accuracy declines, and hallucinations increase as the code size grows. These results suggest that LLMs could play a pivotal role in future security solutions, particularly within code completion frameworks, where they can provide real-time guidance to prevent vulnerabilities. The dataset is accessible at https://github.com/CASTLE-Benchmark.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 4 Pith papers

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. Activation Probes Surface Code-Security Signals that the Model's Output Misses

    cs.CR 2026-08 conditional novelty 6.0 of 10

    A linear probe read from open-weight LLM activations ranks vulnerable Python functions above their fixes on 61-67% of unseen CVEs, outperforming the same models' prompted verdicts.

  2. SecDrift: Measuring Sector-Conditioned Security Drift in AI-Generated Code

    cs.CR 2026-07 accept novelty 6.0 of 10

    Sector-conditioned prompt framing does not significantly change static-analysis vulnerability rates in AI-generated code; the apparent effect is a composition artifact of two CWE categories.

  3. Extracting Recurring Vulnerabilities from Black-Box LLM-Generated Software

    cs.CR 2026-02 reject novelty 5.0 of 10

    Frontend features of LLM-generated apps can predict hidden backend vulnerabilities that a given model tends to reproduce, enabling black-box attack triage.

  4. ATLAS: Multi-View Code Representation Tool for C and C++ Source Programs

    cs.SE 2025-12 conditional novelty 5.0 of 10

    ATLAS claims no-build aligned AST/CFG/DFG extraction for C/C++ at 96.8%/91.7% CFG correctness, and a 34.7-point LLM line-coverage lift when fed its CFG paths.

Pith tools