From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/vividas: Check packet size Date: Thu, 29 Sep 2022 17:45:26 +0200 Message-ID: <20220929154526.GC6583@pb2> (raw) In-Reply-To: <166446062255.22057.14060430318465734011@lain.khirnov.net> [-- Attachment #1.1: Type: text/plain, Size: 2800 bytes --] On Thu, Sep 29, 2022 at 04:10:22PM +0200, Anton Khirnov wrote: > Quoting Michael Niedermayer (2022-09-29 00:35:09) > > On Wed, Sep 28, 2022 at 05:16:05PM +0200, Anton Khirnov wrote: > > > Quoting Michael Niedermayer (2022-09-22 20:08:51) > > > > Fixes: signed integer overflow: 119760682 - -2084600173 cannot be represented in type 'int' > > > > Fixes: 50993/clusterfuzz-testcase-minimized-ffmpeg_dem_VIVIDAS_fuzzer-6745781167587328 > > > > > > > > Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg > > > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > > > --- > > > > libavformat/vividas.c | 13 +++++++++++-- > > > > 1 file changed, 11 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/libavformat/vividas.c b/libavformat/vividas.c > > > > index e9954f73ed0..e8efe49a5c0 100644 > > > > --- a/libavformat/vividas.c > > > > +++ b/libavformat/vividas.c > > > > @@ -683,6 +683,7 @@ static int viv_read_packet(AVFormatContext *s, > > > > > > > > if (viv->sb_entries[viv->current_sb_entry].flag == 0) { > > > > uint64_t v_size = ffio_read_varlen(pb); > > > > + int last, last_start; > > > > > > > > if (!viv->num_audio) > > > > return AVERROR_INVALIDDATA; > > > > @@ -704,14 +705,22 @@ static int viv_read_packet(AVFormatContext *s, > > > > start = ffio_read_varlen(pb); > > > > pcm_bytes = ffio_read_varlen(pb); > > > > > > > > - if (i > 0 && start == 0) > > > > - break; > > > > + if (i > 0) { > > > > + if (start == 0) > > > > + break; > > > > + if (start < last || start - (unsigned)last > INT_MAX) > > > > > > What is the second condition for? > > > > start is signed int so are "copyies" of it > > "start < last" would allow a negative last with a large start > > the 2nd check handles that. > > the difference of consequtive values are stored as int later > > > > The patch tried to leave the storage types and check for it. > > The types could be changed or some other checks could be used > > I was undecided on this patch a bit too. I picked this mainly > > to keep changes more minimal but maybe this was not the best > > choice > > Checking that start >= 0 would fix this as well, wouldn't it? i agree > I don't > think it makes sense for it to be negative. well no, but i tried to minimize the chance of breaking something so the fix ended up looking a bit wonky ill change it to check for start >= 0 thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The worst form of inequality is to try to make unequal things equal. -- Aristotle [-- 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-09-29 15:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 18:08 Michael Niedermayer 2022-09-22 18:08 ` [FFmpeg-devel] [PATCH 2/2] avformat/westwood_vqa: Check chunk size Michael Niedermayer 2022-09-28 15:17 ` Anton Khirnov 2023-10-03 14:07 ` Michael Niedermayer 2022-09-28 15:16 ` [FFmpeg-devel] [PATCH 1/2] avformat/vividas: Check packet size Anton Khirnov 2022-09-28 22:35 ` Michael Niedermayer 2022-09-29 14:10 ` Anton Khirnov 2022-09-29 15:45 ` 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=20220929154526.GC6583@pb2 \ --to=michael@niedermayer.cc \ --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