From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] [mov] Avoid OOM for invalid STCO / CO64 constructions. Date: Thu, 15 Feb 2024 23:35:34 +0100 Message-ID: <20240215223534.GH6420@pb2> (raw) In-Reply-To: <CAPUDrwebThi7Re5GHdAK5u_DmrhuU5mktTFFsWcYXa8GXRob=w@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --] On Thu, Feb 15, 2024 at 12:07:05PM -0800, Dale Curtis wrote: > On Mon, Feb 5, 2024 at 12:07 PM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > assuming atom.size is an arbitrary 64bit value > > then the value of FFMIN() is also 64bit but entries is unsigned 32bit, > > this truncation > > would allow setting entries to values outside whats expected from FFMIN() > > also we seem to disalllow entries == 0 before this > > and its maybe possible to set entries = 0 here, bypassing the == 0 check > > before > > > Thanks. I've moved the clamp up to before the zero check. The only way a > bad 64-bit value could get in is if atom.size < 8, which I didn't think was > possible, but I've added a FFMAX(0,) there too. [...] > + FFMIN(avio_rb32(pb), > + FFMAX(0, (atom.size - 8) / > + (atom.type == MKTAG('s', 't', 'c', 'o') ? 4 : 8))); FFMIN/MAX can evaluate their arguments multiple times so avio_rb32() might be executed more than once thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The real ebay dictionary, page 1 "Used only once" - "Some unspecified defect prevented a second use" "In good condition" - "Can be repaird by experienced expert" "As is" - "You wouldnt want it even if you were payed for it, if you knew ..." [-- 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:[~2024-02-15 22:35 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 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 [this message] 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=20240215223534.GH6420@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