GNOME Bugzilla – Bug 639136
[oggparse]code is not safe when using libogg fuctions
Last modified: 2011-01-24 18:40:26 UTC
Created attachment 177920 [details] [review] make it safer The fuction "gst_ogg_parse_submit_buffer"in file gstoggparse.c using the libogg fuctions:"ogg_sync_buffer, ogg_sync_wrote" to submit the given buffer to the ogg sync, but it didn't judge the return values. That's not safe. So I did this change form the fuction "gst_ogg_demux_submit_buffer" int file gstoggdemux.c Here is the patch:
Created attachment 178008 [details] [review] patch I change the codes, and I think this one could be better
Thanks, I'll push this change after the next gst-plugins-base release.
commit cb9607632f86a28ee7fe649efd279ca07edf4844 Author: Yang Xichuan <xichuan.yang@tieto.com> Date: Tue Jan 11 15:10:42 2011 +0800 oggparse: Make gst_ogg_parse_submit_buffer() safe By not passing zero-sized buffers to ogg_sync_buffer() and checking the return values of libogg functions. Fixes bug #639136.