Fix string handling bug in putenv() #195
Merged
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
GNU Readline 4.3 on stock OpenBSD 7.6 uses putenv(), but the value of envname was not properly null-terminated, leading to setting the incorrect environment variable name.
memreflect
force-pushed
the
putenv-fix
branch
2 times, most recently
from
3b8492c to
9948e44
Compare
Collaborator
|
Good catch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
GNU Readline 4.3 on stock OpenBSD 7.6 uses
putenv(), but the allocated stringenvnameinputenv()was not properly null-terminated, leading to readline trying to set incorrect environment variable names likeLINES{garbage bytes}.