Fix buffer overflow in soundex library #59
Merged
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
No space was allocated for the null terminator in the result buffer. ASan catches this error when running the tests.
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.
No space was allocated for the null terminator in the result buffer. ASan catches this error when running the tests.
There's a potential issue that
d(andi) will overflow, computing an incorrect result, except that they're tied to a VLA and the program would crash via stack overflow well before that point. Especially considering the VLAs (#58), this soundex library is questionable and probably shouldn't be used on untrusted input without careful review and fixes, and VLA removal.