You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I found a potential null pointer dereference bug in the project source code of opusfile related to usage of libogg, and I have shown the execution sequence of the program that may generate the bug on the graph below. The red text illustrates the steps that generate the bug, the red arrows represent the control flow.
in short, the key step is not check the return value of call-statement relate to libogg.
Hi, I found a potential null pointer dereference bug in the project source code of opusfile related to usage of libogg, and I have shown the execution sequence of the program that may generate the bug on the graph below. The red text illustrates the steps that generate the bug, the red arrows represent the control flow.
in short, the key step is not check the return value of call-statement relate to libogg.
opusfile/src/opusfile.c
Lines 2240 to 2246 in a46042a
would you help to check if this bug is true?thank you for your patience and effort.
The text was updated successfully, but these errors were encountered: