Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsArrayEach on non-array root emitted spurious callback before erroring
This defect has been fixed and verified.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- risk area
- Error Handling
Root cause
What actually went wrong underneath — how it is classified, and the coverage gap that let it slip through.
parser.go:ArrayEach lacked a root-token-type guard in the no-keys path. The main loop unconditionally parsed the first token after the assumed `[` as an array element; for object/number input, this misinterpreted the first content byte as an element and invoked the callback with bogus data before the structural-malformed check triggered.
Disposition: Covered by a requirement
Proof it's fixed
The tests, tightened requirements and new obligations that prove this defect is gone — and can't quietly return.
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Nothing to trace into
This finding links no requirements, so there is no dependency graph to follow. Everything we know about it is in the evidence above.
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.