On Mon, Mar 06, 2017 at 03:51:51PM +0100, Michał Krasowski wrote: > It seems that the loop tried to access the memory regions > beyond allocation, what caused crashes in not-so-rare cases, when > the memory read did not belong to current process. > > This change is fixing the out-of-bounds read problem. > Compiling this function with -fsanitize=address and running doesn't > result in sanitizer warning as before. > --- > libavcodec/h2645_parse.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-)
have you seen/read the documentation for AV_INPUT_BUFFER_PADDING_SIZE ? if not, that may be the cause of the issues you see [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Avoid a single point of failure, be that a person or equipment.
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
