From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 4/6] avformat/cafdec: saturate start + size into 64bit Date: Sat, 30 Sep 2023 18:32:07 +0200 Message-ID: <20230930163207.GM3543730@pb2> (raw) In-Reply-To: <ab85ee6f-e46c-4b5f-aeb1-5f273475391e@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1903 bytes --] On Fri, Sep 29, 2023 at 08:41:23PM -0300, James Almer wrote: > On 9/29/2023 8:19 PM, Michael Niedermayer wrote: > > Fixes: signed integer overflow: 64 + 9223372036854775803 cannot be represented in type 'long long' > > Fixes: 51896/clusterfuzz-testcase-minimized-ffmpeg_dem_CAF_fuzzer-6536881135550464 > > > > Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > --- > > libavformat/cafdec.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/libavformat/cafdec.c b/libavformat/cafdec.c > > index e92e3279fc6..0e50a3cfe68 100644 > > --- a/libavformat/cafdec.c > > +++ b/libavformat/cafdec.c > > @@ -435,7 +435,7 @@ static int read_packet(AVFormatContext *s, AVPacket *pkt) > > /* don't read past end of data chunk */ > > if (caf->data_size > 0) { > > - left = (caf->data_start + caf->data_size) - avio_tell(pb); > > + left = av_sat_add64(caf->data_start, caf->data_size) - avio_tell(pb); > > avio_tell(pb) here is guaranteed to be bigger than caf->data_start, which is > the offset where the DATA chunk starts, so the result of this calculation > will be <= INT64_MAX even if you don't saturate it and instead cast it to > uint64_t. Nonetheless, if the DATA chunk ends at an offset that would not > fit in an int64_t, then we can't parse it to begin with due to AVIOContext > API limitations. > > Maybe we should just abort in read_header() if data_start + data_size > > INT64_MAX, instead of pretending we can parse the file, invalid or not, by > saturating values. yes ill try that thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you think the mosad wants you dead since a long time then you are either wrong or dead since a long time. [-- 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".
next prev parent reply other threads:[~2023-09-30 16:32 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-29 23:19 [FFmpeg-devel] [PATCH 1/6] avformat/avidec: support huge durations Michael Niedermayer 2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 2/6] avformat/avidec: Correct unsigend type Michael Niedermayer 2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 3/6] vformat/cafdec: dont seek beyond 64bit Michael Niedermayer 2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 4/6] avformat/cafdec: saturate start + size into 64bit Michael Niedermayer 2023-09-29 23:41 ` James Almer 2023-09-30 16:32 ` Michael Niedermayer [this message] 2024-03-25 22:54 ` Michael Niedermayer 2023-09-29 23:20 ` [FFmpeg-devel] [PATCH 5/6] avformat/dxa: Adjust order of operations around block align Michael Niedermayer 2023-09-29 23:20 ` [FFmpeg-devel] [PATCH 6/6] avformat/iff: Saturate avio_tell() + 12 Michael Niedermayer 2024-03-25 22:58 ` Michael Niedermayer 2023-09-30 9:35 ` [FFmpeg-devel] [PATCH 1/6] avformat/avidec: support huge durations Marton Balint 2023-09-30 14:04 ` Michael Niedermayer 2023-09-30 14:31 ` Michael Niedermayer 2023-09-30 20:18 ` Anton Khirnov 2023-09-30 22:28 ` Michael Niedermayer 2023-10-02 9:07 ` Anton Khirnov 2023-10-02 19:03 ` Michael Niedermayer 2023-10-03 9:10 ` Tomas Härdin 2023-10-03 18:53 ` Michael Niedermayer 2024-03-25 22:50 ` 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=20230930163207.GM3543730@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