MEDIUM: Potentially Unsafe Code - Potential Memory Leak#246
Open
DawmosTomie wants to merge 1 commit intolucasg:masterfrom
Open
MEDIUM: Potentially Unsafe Code - Potential Memory Leak#246DawmosTomie wants to merge 1 commit intolucasg:masterfrom
DawmosTomie wants to merge 1 commit intolucasg:masterfrom
Conversation
|
Seems this is correct. I'm adding this to my fork of dependencies. |
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.
Dear author, Hello!
I found a small security breach,
I've modified it,
I hope you can merge it。
(My English is not very good, I hope the wording does not offend you)
Description-MEDIUM: Potentially Unsafe Code - Potential Memory Leak
Line: 71 - Dependencies\third_party\phlib\jsonc\arraylist.c
Source code may experience memory leaks when attempting to extend arrays.
If the realloc function fails and returns NULL, the original memory is still retained.
Solution
solve this problem by checking the return value of realloc after calling it.
If realloc returns NULL, the original memory should be freed and an error returned.
Modified code