Repository navigation
fix(jsonrpc): reject invalid UTF-8 and trailing request content #7103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
waynercheung
wants to merge
7
commits into
tronprotocol:release_v4.8.3
Choose a base branch
from
waynercheung:fix/jsonrpc-request-body-validation
base: release_v4.8.3
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+244
−17
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
68a580c
fix(jsonrpc): reject invalid UTF-8 request bytes
waynercheung b4bca69
fix(jsonrpc): reject trailing request content
waynercheung 0a577bb
fix(jsonrpc): return a parse error for undecodable request bodies
waynercheung 1d841d4
test(jsonrpc): cover raw two-byte UTF-8 request parameters
waynercheung bf6d23a
fix(jsonrpc): accept only UTF-8 request bodies
waynercheung c2ea817
refactor(jsonrpc): narrow parsing catch to JsonProcessingException
waynercheung dfd2806
test(jsonrpc): drop request body cases already covered by the byte check
waynercheung File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[NIT] Two small things:
wellFormedNonAsciiInput_isDispatchedcovers raw 3-byte and 4-byte UTF-8, but its U+0080 to U+07FF case is the JSON escape for U+00E9, which is plain ASCII on the wire. So no positive test sends a raw 2-byte sequence, and the negative test only has 2-byte overlongs. Consider adding one, e.g.new String(Character.toChars(0xE9)). Optionally,new String(Character.toChars(0x10FFFF))instead of the raw literal on line 141 would make that case visible in the diff; plain Unicode escapes would tripAvoidEscapedUnicodeCharacters.JsonRpcServlet.java:127could also mention code points above U+10FFFF, as the description does.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. 1d841d4 adds a raw two-byte parameter. I used U+07FF rather than U+00E9 because the JSON escape case already decodes to U+00E9 and the per-iteration
verifywould count two calls. The 4-byte parameters are now built withCharacter.toChars. The comment at JsonRpcServlet.java:127 now mentions code points above U+10FFFF (bf6d23a).