fix(security): bound JSON bodies and password length - #70
Merged
Conversation
JSON create and unlock parse only after a hard byte limit. Passwords over 1024 characters are rejected before scrypt to stop CPU DoS. Closes #67
ArianAr
force-pushed
the
fix/67-body-and-password-limits
branch
from
July 15, 2026 23:46
2a318b2 to
860c5b2
Compare
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
readBodyWithLimit/readJsonBodyWithLimitfor create (JSON + stream) and unlockCloses #67
Test plan
pnpm test(128 tests)pnpm lintpnpm typecheckpnpm buildcigreen