[FFmpeg-devel] get_bits overrun checking from Google Chrome patches

Reimar Döffinger Reimar.Doeffinger
Tue Sep 8 10:21:28 CEST 2009


On Tue, Sep 08, 2009 at 01:29:27AM +0100, Robert Swain wrote:
> I'm actually a little surprised we didn't spot and remedy this
> earlier. Any suggestions for any cleaner solutions than Google's
> proposition?

Yes, fix the codecs to explicitly check for buffer end at the appropriate
(codec-specific!) points, taking advantage of the fact that buffers are
0-padded.



More information about the ffmpeg-devel mailing list