security(json): Add nesting depth limit to prevent stack overflow #2745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a nesting depth limit to the JSON parser to fix a security vulnerability.
Without a depth limit, parsing a deeply nested JSON string can lead to a stack overflow, which crashes the program. This can be used as a DoS attack.
This is a common security measure found in many other languages and libraries (like Go, Rust, and Python) to ensure safe JSON parsing. This change makes moonbit json parser more robust and secure.