Hi, On Wed, Aug 17, 2022 at 4:32 PM Martin Storsjö <mar...@martin.st> wrote:
> This avoids overflows on some inputs in the x86 case, where the > assembly version would clip/overflow differently from the > C reference function. > > This doesn't seem to be a real issue with actual input data, but > only with the previous fully random input data. > I'm a bit scared of this change... If we can trigger overflows with specific pixel patterns, doesn't that make FFmpeg input-data exploitable? Think of how that would go with corporate users with user-provided input data. Ronald _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
