fix missing null termination in exepath string #32
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.
In
find_exe_realpath
whenrealexe
is copied toexepath
, there is no null termination. Thewcsncpy
function will only result in a null terminated string if a null is copied from the source to the destination. If the characters copied do not include a terminating null, it must be appended manually. Because exepath is uninitialized, the string will only terminate if the memory happened to have nulls at the position where the path ends.Because the wrapper typically has a short life-span, the memory may generally be clean, but hook DLLs can leave it dirty enough to trigger this defect. In the case of git-for-windows/git#1855 this resulted in a child process bomb due to the garbage data later being acted upon due to dirty released memory from an Nvidia driver process hook.