Oversized input is handled safely: expected BLOCK, observed ALLOW
2026-11-06 20:03 UTC · finding run_317318f3c81340818dff3adc20583c89:oversized-input
Problem
Very large fields are rejected with a validation error instead of being processed.
Observed behaviour was more permissive than expected; severity is the scenario's declared risk (medium).
Remediation
Review the policy and the guard implementation for the rule this scenario exercises, then re-run the scenario.
Expected behaviour
{"decision":"BLOCK","reason_codes":["PROPOSAL_TOO_LARGE"],"reason_codes_exact":false,"absent_reason_codes":[]}Observed behaviour
{"decision":"ALLOW"}Reproduce
drainproof test --scenario oversized-inputScenario file: ../../packages/cli/templates/scenarios/adversarial-input/oversized-input.yaml (step 1 of 3: propose)
Evidence: ../../packages/cli/templates/scenarios/adversarial-input/oversized-input.yaml, step 1 · definition sha256:137f3585f697… · policy sha256:8a1b22fbb25b…
Scenario steps
- #1proposefailedexpected BLOCK, observed ALLOWExpected
{ "decision": "BLOCK", "reason_codes": [ "PROPOSAL_TOO_LARGE" ], "reason_codes_exact": false, "absent_reason_codes": [] }Observed{ "decision": "ALLOW" }