5b-poc-validator

Compile and run all PoCs listed in the manifest. This agent handles bulk compilation and execution, producing runtime results that are subsequently checked by the verification agent (5c-poc-verifier) for semantic correctness.

Input

You receive these values from the orchestrator:

Parameter	Description
workdir	Run working directory (e.g. /tmp/zeroize-audit-{run_id}/)
config_path	Path to {workdir}/merged-config.yaml

Process

Step 0 — Load Configuration

Read config_path to access PoC-related settings.

Step 1 — Read Manifest

Read {workdir}/poc/poc_manifest.json. Collect all PoC entries.

If no PoCs exist, write an empty results file and exit.

Step 2 — Compile and Run Each PoC

Dispatch on poc_entry.language:

C/C++ PoCs (language is absent or "c")

1. Compile:

   cd {workdir}/poc && make <makefile_target>
   

2. If compilation succeeds, run and record exit code:

   cd {workdir}/poc && ./<makefile_target>
   echo "Exit code: $?"
   

3. Record result: {finding_id, category, language: "c", poc_file, compile_success, exit_code}.

Rust PoCs (language == "rust")

Rust PoCs use cargo test. The exit code convention maps directly: a passing assert! → test passes → cargo exits 0 → exploitable; a failing assert! (panic) → test fails → cargo exits non-zero → not exploitable.

1. Compile check (no run):

   <poc_entry.compile_cmd>
   # e.g. cargo test --manifest-path {workdir}/poc/Cargo.toml --no-run --test za_0001_missing_source_zeroize
   

2. If compilation succeeds, run the specific test and record exit code:

   <poc_entry.run_cmd>
   # e.g. cargo test --manifest-path {workdir}/poc/Cargo.toml --test za_0001_missing_source_zeroize -- --nocapture
   echo "Exit code: $?"
   

3. Capture stdout/stderr from the cargo test run and include in the result for the verifier.

4. Record result: `{finding_id, category, languag