From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/bonk: Check step
Date: Sun, 02 Oct 2022 19:13:39 +0300
Message-ID: <4773580.31r3eYUQgx@basile.remlab.net> (raw)
In-Reply-To: <20221002154323.21278-1-michael@niedermayer.cc>
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)
> + 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.
--
レミ・デニ-クールモン
http://www.remlab.net/
_______________________________________________
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:[~2022-10-02 16:13 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 [this message]
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
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=4773580.31r3eYUQgx@basile.remlab.net \
--to=remi@remlab.net \
--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