From: Kacper Michajlow <kasper93@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/jpegxl_parser: add sanity check for frame size Date: Wed, 16 Jul 2025 12:34:18 +0200 Message-ID: <CABPLASSzT8UPf9psdn6QSE7hzvRzDLeNNrHS1QBZK=897y+e-w@mail.gmail.com> (raw) In-Reply-To: <20250715180226.63221-1-leo.izen@gmail.com> On Tue, 15 Jul 2025 at 20:02, Leo Izen <leo.izen@gmail.com> wrote: > > If a frame size is absolutely massive, this can spin the parser as it > attempts to decode a permuted TOC. We add a sanity check here for eight > times the size of the image for an internal frame to prevent malicious > bitstreams from slowing the parser down to a crawl. > > Signed-off-by: Leo Izen <leo.izen@gmail.com> > Reported-by: Kacper Michajłow <kasper93-at-gmail.com@ffmpeg.org> Please use my real email, instead this wrapped one, thanks. > --- > libavcodec/jpegxl_parser.c | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/jpegxl_parser.c b/libavcodec/jpegxl_parser.c > index 68404229a5..e40b4fbf96 100644 > --- a/libavcodec/jpegxl_parser.c > +++ b/libavcodec/jpegxl_parser.c > @@ -1315,6 +1315,11 @@ static int parse_frame_header(void *avctx, JXLParseContext *ctx, GetBitContext * > if (get_bits1(gb)) { > JXLEntropyDecoder dec; > int64_t end, lehmer = 0; > + /* parser sanity check to prevent TOC perm from spinning cpu */ > + if (width > meta->coded_width * 8 || height > meta->coded_height * 8) { > + av_log(avctx, AV_LOG_WARNING, "massive frame detectived, aborting parser\n"); detected? Also maybe make it more formal like "frame of size %dx%d exceeds limit of %dx%d, aborting" or something along those lines. "massive frame" doesn't really tell much. - Kacper _______________________________________________ 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:[~2025-07-16 10:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-15 18:02 Leo Izen 2025-07-16 10:34 ` Kacper Michajlow [this message] 2025-07-16 17:50 ` Leo Izen
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='CABPLASSzT8UPf9psdn6QSE7hzvRzDLeNNrHS1QBZK=897y+e-w@mail.gmail.com' \ --to=kasper93@gmail.com \ --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