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.
https://github.com/xiph/opusfile/blob/a46042a92cdf318496da0fa0d67a2d1c27ce15b5/src/opusfile.c#L2240-L2246
would you help to check if this bug is true?thank you for your patience and effort.
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.
https://github.com/xiph/opusfile/blob/a46042a92cdf318496da0fa0d67a2d1c27ce15b5/src/opusfile.c#L2240-L2246
would you help to check if this bug is true?thank you for your patience and effort.