Skip to content
Drainproof
Demo mode. These reports are fixtures generated by running the Drainproof CLI against the bundled example policies. They are not results from your project.

← Run run_317318f3

Invalid decimal formats are rejected: expected BLOCK, observed ALLOW

2026-11-06 20:03 UTC · finding run_317318f3c81340818dff3adc20583c89:invalid-decimal-formats

high

Problem

Exponents, thousands separators, hex, leading/trailing dots, non-finite values and unquoted (floating-point) numbers must be rejected rather than coerced.

Observed behaviour was more permissive than expected; severity is the scenario's declared risk (high).

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":["AMOUNT_INVALID"],"reason_codes_exact":false,"absent_reason_codes":[]}

Observed behaviour

{"decision":"ALLOW"}

Reproduce

  1. drainproof test --scenario invalid-decimal-formats
  2. Scenario file: ../../packages/cli/templates/scenarios/adversarial-input/invalid-decimal-formats.yaml (step 1 of 6: propose)

Evidence: ../../packages/cli/templates/scenarios/adversarial-input/invalid-decimal-formats.yaml, step 1 · definition sha256:94cdb8704bd0… · policy sha256:8a1b22fbb25b…

Scenario steps

  1. #1proposefailedexpected BLOCK, observed ALLOW
    Expected
    {
      "decision": "BLOCK",
      "reason_codes": [
        "AMOUNT_INVALID"
      ],
      "reason_codes_exact": false,
      "absent_reason_codes": []
    }
    Observed
    {
      "decision": "ALLOW"
    }