[XviD-devel] Fw: buffer overflow in userdata parser

[Christoph Lampert]

On Wed, 19 Jan 2005, suxen_drol wrote:
> 
> side note: isn't 256 bytes overkill. the largest
> string we have to process is going to be
> something like "DivX503Build99999p". even in we
> extend the integers to 2^32, there still less
> than 32 bytes to process..

One day, there might be postprocessing or other data included. 

chl