lambdaclass / lambdaclass/lambda_compiler_kit
JSON parser DoS prevention
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
As reported by Claude review, our current JSON parser does not prevent large exponents from exhausting our memory.
The solution proposed by Claude, however, is inflexible: cap the exponent.
For most regular uses that would be OK. For schema validation, though, that might be too restrictive.
Instead, I suggest we just keep the exponent as a separate field for JSON numbers.
The trade off:
- We get arbitrarily large numbers with efficient-ish representation
- We allow users to define schemas with arbitrary numbers
- We need to implement basic operations and might need some float-like behavior in places
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the JSON parser and its number representation, then determine the scope of preserving exponents and the required basic operations; done means large exponents no longer cause memory exhaustion while schema validation still accepts arbitrary numbers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- compilers, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100