erlang: Fix crash parsing directives longer than 31 characters #3726
Conversation
This file contains 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
Even if they might not exist, fix the code not to crash on them. The issue was that the pointer to the vString buffer holding the directive name was cached at its value right after the vString creation, yet that buffer might get realloc()ated if it grows past the initial length of 32, possibly making the initial pointer invalid. Fix this by simply getting the pointer to the value later on.
masatake
approved these changes
May 15, 2023
|
Thank you. |
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.
Even if they might not exist, fix the code not to crash on them.
The issue was that the pointer to the vString buffer holding the directive name was cached at its value right after the vString creation, yet that buffer might get realloc()ated if it grows past the initial length of 32, possibly making the initial pointer invalid.
Fix this by simply getting the pointer to the value later on.