- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CoSA-Drive is a runtime defense framework for driving VLAs under visual, temporal, state, task, and cross-modal corruption. Different repair operators generate behavior candidates from a frozen driving model. CERA scores each candidate's safety, intervention-induced harm, and utility using runtime evidence and an ensemble uncertainty estimate. A deterministic DriveContract module then vetoes constraint violations, with replanning or minimum-risk fallback when necessary. The paper reports NAVSIM PDM increasing from 0.7503 under attack to 0.8399, with unsafe outcomes decreasing from 25.66% to 11.71%. Reactive CARLA experiments and tests on four VLA backends show additional recovery and safety benefits.
Critical strengths
-
The behavior-level decision structure targets a real weakness in restoration-only defenses. Evaluating the consequences of multiple admissible interventions, while reserving final veto authority for a separate checker, is a sensible architecture (Sections 4.3–4.7). The NAVSIM comparison shows that visual restoration alone reduces PDM while candidate authorization improves both PDM and proxy safety (Table 2). Explicit utility and new-harm heads also address the risk that nominally conservative defenses merely stop the vehicle.
-
The evaluation includes reactive outcomes and acknowledges selective-execution trade-offs. The CARLA studies compare restoration, shielding, component removal, and the full system; the appendix reports route-clustered uncertainty rather than treating correlated frames as independent observations (Tables 3, 5–6; Figure 11). Figure 11 supports improvements in red-light violations and any safety violation over Shield-only. Risk–coverage curves and target-backend calibration details further improve interpretability (Appendices D and G). These are substantial strengths relative to evaluating only image repair or trajectory similarity.
Critical weaknesses
-
The operational problem and distinct contribution are insufficiently specified. Although the paper motivates evaluating behavior after input repair, the concrete authorization problem remains difficult to reconstruct: which runtime evidence is trustworthy, how candidate safety is labeled and predicted, and how learned authorization differs from the deterministic checker are not specified sufficiently. This makes it difficult to assess whether CERA introduces a substantive advance over conventional candidate scoring and safety filtering.
-
Comparison with established defense methods is insufficient. The experiments include restoration-only, shielding-only, and internal ablation baselines, but do not clearly identify implementations of previously published defense or runtime-assurance methods. Consequently, the results establish benefits over the selected simplified configurations without demonstrating an advantage over existing approaches. Comparisons with matched access to trusted evidence, candidate behaviors, and fallback mechanisms are particularly important.
Questions for authors
-
Can the authors provide a concrete end-to-end example specifying corrupted inputs, trusted runtime evidence, candidate trajectories, CERA scores, and the final DriveContract decision? What distinguishes the proposed authorization mechanism from standard learned candidate selection followed by safety filtering?
-
Which experimental baselines implement previously published methods? How does CoSA-Drive compare with the closest applicable approach under matched information, candidate-generation, and fallback conditions?