Legacy JSONL decoder accepts leading-zero numbers #632
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES#632
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The legacy JSONL parser accepts leading-zero numeric literals. At
4cbd403dc207c46f8b21273b141d16b2470105e9, changing the first canonical v3 fixture record from"v":3to"v":03still returns a successful EventLogRecord. JSON integers do not permit a leading zero before another digit. This weakens the strict log boundary needed before research event replay.Reproduction
Use
decode_event_log_record_jsonlon the first record oftests/fixtures/legacy_phase1/root_revoke/direct/v3/events.jsonl, then insert0immediately after"v":. The probe printscanonical_accepted=1 leading_zero_accepted=1and exits 1. The standalone probe and output are retained in the local execution audit; a regression test will cover all supported legacy schema versions.Scope
Reject non-JSON numeric spelling and audit JSON whitespace recognition at the same lexical boundary. Preserve canonical legacy encodings, event semantics, archived fixture bytes and the separate version-4 implementation. Malformed input must return ParseError without partial records.
Steps