Consider null terminator when using malloc #91
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
13 tasks
TomaSajt
force-pushed
the
master
branch
2 times, most recently
from
b62600c to
477c036
Compare
|
Thanks, looks like I missed that when allocating memory. I will merge this so you can package it for nixpkg! |
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.
I was trying to package this program for
Nixpkgs, and used its custom meson builder script, which uses some kind of fortification by default, which catches buffer overflows.When running the program I got several buffer overflow errors, and with the help of
coredumpctlI could trace it back to some string size math. It looks like there wasn't enough space for the null-terminator of the string.