Prevent header NV allocation size overflow - #547
Open
freedom-winds wants to merge 1 commit into
Open
Conversation
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
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
Add overflow checks to
nghttp3_nva_copybefore allocating storage for copied header names, values, and the NV array.Details
nghttp3_nva_copypreviously accumulated allocation sizes without checking integer overflow. Craftednamelen,valuelen, ornvlenvalues could wrap the calculated size, resulting in an undersized allocation followed by out-of-bounds memory writes during header copying.This patch:
nvlen * sizeof(nghttp3_nv).NGHTTP3_ERR_INVALID_ARGUMENTfor overflowing inputs.Validation
The modified source passes compiler syntax validation with
-Wall -Wextra -Werror.