From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/4] avcodec/cbs_vp8: Do not use assert to check for end Date: Sat, 16 Dec 2023 09:20:24 -0300 Message-ID: <67b46620-8a26-472b-93b9-29b51928464b@gmail.com> (raw) In-Reply-To: <20231216121619.19436-2-michael@niedermayer.cc> On 12/16/2023 9:16 AM, Michael Niedermayer wrote: > Fixes: abort() > Fixes: 64232/clusterfuzz-testcase-minimized-ffmpeg_BSF_TRACE_HEADERS_fuzzer-5417957987319808 > > Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > libavcodec/cbs_vp8.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/cbs_vp8.c b/libavcodec/cbs_vp8.c > index 01d4b9cefef..b76cde98517 100644 > --- a/libavcodec/cbs_vp8.c > +++ b/libavcodec/cbs_vp8.c > @@ -329,7 +329,9 @@ static int cbs_vp8_read_unit(CodedBitstreamContext *ctx, > > pos = get_bits_count(&gbc); > pos /= 8; > - av_assert0(pos <= unit->data_size); > + > + if (pos > unit->data_size) > + return AVERROR_INVALIDDATA; Wouldn't this be hiding a bug in the parsing code? The assert is there to ensure no overread happened. > > frame->data_ref = av_buffer_ref(unit->data_ref); > if (!frame->data_ref) _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-12-16 12:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-16 12:16 [FFmpeg-devel] [PATCH 1/4] tools/target_dec_fuzzer: Adjust Threshold for VP6A Michael Niedermayer 2023-12-16 12:16 ` [FFmpeg-devel] [PATCH 2/4] avcodec/cbs_vp8: Do not use assert to check for end Michael Niedermayer 2023-12-16 12:20 ` James Almer [this message] 2023-12-17 12:09 ` Michael Niedermayer 2023-12-18 11:57 ` Dai, Jianhui J 2023-12-16 12:16 ` [FFmpeg-devel] [PATCH 3/4] avcodec/jpeglsdec: Check Jpeg-LS LSE Michael Niedermayer 2023-12-29 0:02 ` Michael Niedermayer 2023-12-16 12:16 ` [FFmpeg-devel] [PATCH 4/4] avformat/mov: do not set sign bit for chunk_offsets Michael Niedermayer 2023-12-29 0:02 ` Michael Niedermayer 2023-12-29 0:01 ` [FFmpeg-devel] [PATCH 1/4] tools/target_dec_fuzzer: Adjust Threshold for VP6A Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=67b46620-8a26-472b-93b9-29b51928464b@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git