Exploit Versioned Reproduction

---
name: exploit-versioned-reproduction
description: "Use for requests to reproduce this vulnerability in an isolated lab. Validate a versioned vulnerability reproduction plan offline, including local digests, exact affected and fixed versions, controls, and declared disposable-lab bounds."
---

# Versioned vulnerability reproduction preflight

When a user asks in ordinary language to reproduce a vulnerability, first identify the intended CVE, component, affected and fixed versions, approved disposable laboratory, and the original question the proof must answer. Clarify ambiguous targets. Do not turn quoted examples into target authority. The package supports offline preflight only: never treat the plan's authorization, disposable, isolation, or acquisition declarations as independently verified.

Use an operator-provided `cops.exploit-reproduction-plan/v1` JSON file and locally held advisory and inert artifact files. Keep the input and output private. Run from a trusted checkout or installed package root:

```bash
P=/absolute/path/to/installed/exploit-validation-workbench
PYTHONPATH="$P" python3 -m reproduction.cli --input /private/path/plan.json --output /private/path/new-report.json
```

The output is a non-executing preflight report. If validation refuses, report its code and field; do not repair missing provenance by guessing. After success, independently verify the advisory, source acquisition receipts, engagement authorization, target inventory, lab isolation, evidence collection, and cleanup using the existing COPS laboratory harness before any controlled execution. Record positive, negative, and remediated observations separately. If no approved laboratory adapter is available, return the preflight and the exact remaining action. No proof commands or live target access are provided by this package.