Fix 1-byte buffer overflow in DONUT_INSTANCE.etwRet64 - #177
Open
its-mr-monday wants to merge 1 commit into
Open
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
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.
Summary
Fixes a buffer overflow in
include/donut.hwhereetwRet64is declared as a 1-byte array butstrcpyindonut.c:983writes 2 bytes (the\xc3byte plus null terminator).The Bug
This causes a 1-byte overflow into the adjacent etwRet32 field. On most Linux systems this goes unnoticed because etwRet32 is immediately overwritten afterward, but platforms with fortified libc (macOS, some hardened Linux distributions) detect this at runtime and abort.
The Fix
Change the buffer size from 1 to 2 bytes to accommodate the null terminator.
Impact
Testing
Verified the fix allows successful shellcode generation on macOS where it previously crashed.