Fix possible corruption in sdsResize (CVE-2023-41056)#12924
Merged
oranagra merged 1 commit intoredis:unstablefrom Jan 9, 2024
oranagra:fix_sdsResize
Merged
Fix possible corruption in sdsResize (CVE-2023-41056)#12924oranagra merged 1 commit intoredis:unstablefrom oranagra:fix_sdsResize
oranagra merged 1 commit intoredis:unstablefrom
oranagra:fix_sdsResize
Conversation
#11766 introduced a bug in sdsResize where it could forget to update the sds type in the sds header and then cause an overflow in sdsalloc. it looks like the only implication of that is a possible assertion in HLL, but it's hard to rule out possible heap corruption issues with clientsCronResizeQueryBuffer
enjoy-binbin
approved these changes
Jan 9, 2024
yossigo
approved these changes
Jan 9, 2024
if redis5.0.5 also has this question （CVE-2023-41056），I don‘t find this function sdsResize in sds.c. |
Collaborator
|
@zhaochunxue this only affects version 7.0.x, and 7.2.x. |
ok,thank you |
roggervalf
pushed a commit
to roggervalf/redis
that referenced
this pull request
Feb 11, 2024
redis#11766 introduced a bug in sdsResize where it could forget to update the sds type in the sds header and then cause an overflow in sdsalloc. it looks like the only implication of that is a possible assertion in HLL, but it's hard to rule out possible heap corruption issues with clientsCronResizeQueryBuffer
funny-dog
pushed a commit
to funny-dog/redis
that referenced
this pull request
Sep 17, 2025
redis#11766 introduced a bug in sdsResize where it could forget to update the sds type in the sds header and then cause an overflow in sdsalloc. it looks like the only implication of that is a possible assertion in HLL, but it's hard to rule out possible heap corruption issues with clientsCronResizeQueryBuffer
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
5 participants
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.
#11766 introduced a bug in sdsResize where it could forget to update the sds type in the sds header and then cause an overflow in sdsalloc. it looks like the only implication of that is a possible assertion in HLL, but it's hard to rule out possible heap corruption issues with clientsCronResizeQueryBuffer