From: Dale Curtis <dalecurtis@chromium.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] [mov] Avoid OOM for invalid STCO / CO64 constructions. Date: Fri, 2 Feb 2024 15:42:35 -0800 Message-ID: <CAPUDrwdoMLQvjDE_DQ2h+HQLGbo6LCJM1kqaNaheh64koTQrVA@mail.gmail.com> (raw) In-Reply-To: <AS8P250MB07447AE5D2E43E094D5DDCEC8F422@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On Fri, Feb 2, 2024 at 3:20 PM Andreas Rheinhardt < andreas.rheinhardt@outlook.com> wrote: > Dale Curtis: > > + // Clamp allocation size for `chunk_offsets` -- don't throw an > error for an > > + // invalid count since the EOF path doesn't throw either. > > + entries = > > + FFMIN(entries, FFMIN(atom.size - 8, avio_size(pb) - > avio_tell(pb)) / > > + (atom.type == MKTAG('s', 't', 'c', 'o') ? 4 > : 8)); > > + > > This may call avio_size() and avio_tell() multiple times. Furthermore, > is it even certain that avio_size() returns a sane value? > I hope so since there are other usages of avio_size() throughout the file in a similar manner. I guess you're saying it may be invalid when !AVIO_SEEKABLE_NORMAL? Sticking to just atom.size is also fine. > > - Andreas > > _______________________________________________ > 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". > _______________________________________________ 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:[~2024-02-02 23:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 23:09 Dale Curtis 2024-02-02 23:22 ` Andreas Rheinhardt 2024-02-02 23:42 ` Dale Curtis [this message] 2024-02-02 23:45 ` Dale Curtis 2024-02-05 20:07 ` Michael Niedermayer 2024-02-15 20:07 ` Dale Curtis 2024-02-15 22:35 ` Michael Niedermayer 2024-02-16 21:41 ` Dale Curtis 2024-02-21 17:27 ` 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=CAPUDrwdoMLQvjDE_DQ2h+HQLGbo6LCJM1kqaNaheh64koTQrVA@mail.gmail.com \ --to=dalecurtis@chromium.org \ --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