Fix double free vulnerability#10
Open
RegularRabbit05 wants to merge 2 commits intojosephpal:masterfrom
Open
Conversation
There was a problem hiding this comment.
Pull request overview
This PR fixes a critical double-free vulnerability in the Cipher class by converting privateCipherKey from a dynamically allocated char* pointer to a stack-allocated char[17] array. This change eliminates undefined behavior caused by attempting to delete string literals or stack-allocated strings.
Key Changes:
- Changed
privateCipherKeyfrom a pointer to a fixed-size array (17 characters including null terminator) - Removed the destructor implementation that was causing the double-free issue
- Updated parameter types to
const char*for better const-correctness - Removed the
CIPHER_DEBUGdefine and moved the default key to a macro
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| src/Cipher.h | Changed privateCipherKey to a stack-allocated array, made constructor/setKey parameters const, and replaced manual destructor with default destructor |
| src/Cipher.cpp | Updated key management to use strcpy() instead of pointer assignment, replaced destructor logic, and added CIPHER_DEFAULT_KEY macro |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.
Your current ~Cipher will run a delete operation on a stack string or your constant, shared, example key which results in undefined behavior (perhaps this is the cause of) #9
I've moved the private key to a standard char array that will be allocated on the stack (if Cipher is created without "new" obviously, else it will be in the heap but in the same memory region) which doesn't need a destructor. I've also removed the DEBUG constant as the user should enable it manually outside the library so that using it in the ide will be easier and moved your shared key to a macro for simplicity.