From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Piotr Bandurski <ami_stuff@o2.pl> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/bonk: Check step Date: Mon, 3 Oct 2022 16:49:55 +0200 Message-ID: <20221003144955.GL6583@pb2> (raw) In-Reply-To: <4773580.31r3eYUQgx@basile.remlab.net> [-- Attachment #1.1: Type: text/plain, Size: 2614 bytes --] On Sun, Oct 02, 2022 at 07:13:39PM +0300, Rémi Denis-Courmont wrote: > Le sunnuntaina 2. lokakuuta 2022, 18.43.23 EEST Michael Niedermayer a écrit : > > Fixes: signed integer overflow: 2040812214 + 255101526 cannot be represented > > in type 'int' Fixes: > > 51323/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_BONK_fuzzer-4791481 > > 067503616 > > > > Found-by: continuous fuzzing process > > https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > --- > > libavcodec/bonk.c | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/libavcodec/bonk.c b/libavcodec/bonk.c > > index 409694f710d..32f7c9b9bdb 100644 > > --- a/libavcodec/bonk.c > > +++ b/libavcodec/bonk.c > > @@ -187,6 +187,9 @@ static int intlist_read(BonkContext *s, int *buf, int > > entries, int base_2_part) if (!dominant) > > n_zeros += steplet; > > > > + if (step > INT_MAX/9*8) if you want the exact limit for any INT_MAX its: (INT_MAX + 1ULL) / 9 * 8 + (INT_MAX + 1ULL) % 9 - 1; though probably a fixed bit value would be better anyway for reproducability > > + return AVERROR_INVALIDDATA; > > + > > step += step / 8; > > } else if (steplet > 0) { > > int actual_run = read_uint_max(s, steplet - 1); > > No problem with this patch *specifically* but wouldn't it be more effective to > fix that sort of issue with checked arithmetic, e.g. something like: > > if (av_ckd_add(&step, step, step / 8)) > return AVERROR_INVALIDDATA; > > ...especially on 64-bit systems whence this is really just an add. This also > avoids having to figure out what the exact boundary value is. If someone has a set of testfiles for this decoder then I can look at this and cleanup the code more completely. i dont know if a step > C vs overflow check is better but i have the suspicion there are more problems as multiple statments around this seem unreachable. And iam also missing some check that i would expect to be in there I found links to datafilehost.com to test files but they are all expired so i have no test files, so iam a bit cautious with changes ... CCing piotr who linked to the files on datafilehost, maybe he still has them. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB In fact, the RIAA has been known to suggest that students drop out of college or go to community college in order to be able to afford settlements. -- The RIAA [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
prev parent reply other threads:[~2022-10-03 14:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-02 15:43 Michael Niedermayer 2022-10-02 16:13 ` Rémi Denis-Courmont 2022-10-02 16:26 ` James Almer 2022-10-02 16:38 ` Andreas Rheinhardt 2022-10-02 17:02 ` Rémi Denis-Courmont 2022-10-03 14:49 ` Michael Niedermayer [this message]
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=20221003144955.GL6583@pb2 \ --to=michael@niedermayer.cc \ --cc=ami_stuff@o2.pl \ --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