fix: add NULL-checks for shared buffer allocation in ngx_rtmp_live_av #1793
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.
The Svace static analysis tool identified a potential issue in the function
ngx_rtmp_live_av
, where the return value ofngx_rtmp_append_shared_bufs
andngx_rtmp_alloc_shared_bufs
is not checked properly. After allocation or appending the value is sending to the functionngx_rtmp_prepare_message
(orngx_rtmp_send_message
) which can cause the null-dereference.So the solution is to add null-checking, like there: