react-doctor/import-metadata-execution-risk

Evaluating imported metadata or file contents (EXIF, manifests, presets, uploads, archives) as code lets an attacker achieve remote code execution.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires when an execution sink: eval, new Function, vm.runIn…, or child_process/cp.exec/spawn (and, when the file also imports a process module like child_process/execa/subprocess/Deno.run, a bare exec(File)(Sync)/spawn(Sync)(): is followed inside the same statement (≤200 chars, no ;) by a lowercase taint word: exif, metadata, manifest, preset, plugin, upload, dropped/drops, archive, zip, unzip, or untar. Comments are stripped before matching.

Suppress when: the taint word is a quoted string-literal argument (e.g. spawnSync('claude', ['plugin', …])): static argument values are not matched: or it is part of a SCREAMING_CASE constant (PLUGIN_ID) or camelCase type (WorkflowMetadata), which the case-sensitive match excludes; a bare spawn(/exec( with no process-module evidence (xstate/redux-saga effects) is also ignored.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Never pass imported or derived metadata into an execution sink. Parse EXIF, manifests, and presets with a real parser and validate them against a strict schema (for example Zod) before use; extract archives with a library that writes to a sandboxed directory and checks for path and zip-slip traversal. If a subprocess is truly required, run a fixed binary with an explicit, validated argument array (never a shell string) and pass the metadata as inert data, not as the command.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.