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: Wed, 21 Feb 2024 18:27:29 +0100 Message-ID: <20240221172729.GB6420@pb2> (raw) In-Reply-To: <CAPUDrwf_Lf4MgH0Ht=Lv2Y9bK6FuXKekJgyX64r9epa9AX=a8Q@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1284 bytes --] On Fri, Feb 16, 2024 at 01:41:35PM -0800, Dale Curtis wrote: > On Thu, Feb 15, 2024 at 2:35 PM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > FFMIN/MAX can evaluate their arguments multiple times so avio_rb32() might > > be executed more than once > > > > Thanks. Good catch. Fixed. > mov.c | 7 +++++++ > 1 file changed, 7 insertions(+) > 08ba396380cc14f3df2bdd4a638c43c1c521b8fc stco-clamp-entries-v4.patch > From b94e542582e375025c59862cee58ec45d39c9cd6 Mon Sep 17 00:00:00 2001 > From: Dale Curtis <dalecurtis@chromium.org> > Date: Fri, 2 Feb 2024 20:49:44 +0000 > Subject: [PATCH] [mov] Avoid OOM for invalid STCO / CO64 constructions. > > The `entries` value is read directly from the stream and used to > allocate memory. This change clamps `entries` to however many are > possible in the remaining atom or file size (whichever is smallest). > > Fixes https://crbug.com/1429357 > > Signed-off-by: Dale Curtis <dalecurtis@chromium.org> > --- > libavformat/mov.c | 7 +++++++ > 1 file changed, 7 insertions(+) will apply thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is a danger to trust the dream we wish for rather than the science we have, -- Dr. Kenneth Brown [-- 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:[~2024-02-21 17:27 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 2024-02-16 21:41 ` Dale Curtis 2024-02-21 17:27 ` 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=20240221172729.GB6420@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