forked from chromium/crashpad
-
Notifications
You must be signed in to change notification settings - Fork 52
fix(win): remove MAX_PATH dependency
#135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: The buffer allocation for
path_bufferuses integer division onpath_length_byteswithout validating its divisibility bysizeof(wchar_t), potentially creating an undersized buffer.Description: In
HandleAddAttachmentV2andHandleRemoveAttachmentV2, the buffer for an attachment path is allocated usingpath_length_bytes / sizeof(wchar_t). This calculation uses integer division, which truncates the result. If the server receives apath_length_bytesvalue from a client that is not evenly divisible bysizeof(wchar_t)(2 bytes), the allocatedpath_bufferwill be smaller thanpath_length_bytes. The subsequent call toLoggingReadFileExactlyattempts to read the fullpath_length_bytesinto this undersized buffer, causing a heap buffer overflow. This can lead to memory corruption or a crash of the exception handler server.Suggested fix: Before allocating the buffer in
HandleAddAttachmentV2andHandleRemoveAttachmentV2, add a check to validate thatpath_length_bytesis evenly divisible bysizeof(wchar_t). If the check fails, log an error and return early to prevent the allocation and subsequent buffer overflow.severity: 0.85, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we can be sure that our untampered client will send bytes that are multiples of
wchar_t, since it is IPC, we should protect against malicious or corrupted input. I will add further validation of the incoming message.