fix: segfault when getcwd is called with null buf #5
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
ruby and I'm guessing other apps pass a null buffer to getcwd, expecting to use the return value rather than having data written into the destination buffer. this obviously causes an illegal access. this patch fixes it by having fakedir's getcwd check if the destination buffer is valid and allocating a new buffer with strdup if it isn't.
Thesola10
added a commit
to nixie-dev/nixie
that referenced
this pull request
Aug 12, 2024
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.
ruby and I'm guessing other apps pass a null buffer to getcwd, expecting to use the return value rather than having data written into the destination buffer. this obviously causes an illegal access. this patch fixes it by having fakedir's getcwd check if the destination buffer is valid and allocating a new buffer with strdup if it isn't.