Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Pavel Roslyy <roslypav-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/usmdec: add support for HCA stream decryption
Date: Fri, 27 Jun 2025 12:20:11 -0700
Message-ID: <CAMM0M58vH6EnJPPJtAXrKvw1Lu5zRWQ0BtOf6YKZ_Hx+TPievA@mail.gmail.com> (raw)
In-Reply-To: <20250626210807.GF29660@pb2>

On Thu, Jun 26, 2025 at 2:08 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi Pavel
>
> On Thu, Jun 26, 2025 at 12:04:17AM -0700, Pavel Roslyy wrote:
> > On Wed, Jun 25, 2025 at 3:40 PM Michael Niedermayer
> > <michael@niedermayer.cc> wrote:
> > >
> > > [...]
> > >
> > > bug found, not applying yet
> > >
> > > ret = ff_alloc_extradata(par, pkt_size + key_buf);
> > >
> > > pkt_size + key_buf can overflow i think
> >
> > If I'm understanding right, I don't think it can.
> > pkt_size = chunk_size - (ret - chunk_start) - padding_size;
> >
> > (ret - chunk_start) should be at least 24 at this point, and I don't think
> > padding_size will be negative so pkt_size is at most UINT32_MAX - 24.
>
> chunk_size is arbitrary 32bit thus pkt_size is arbitrary 32bit
>
>
> >
> > key_buf adds at most 10, which is not enough to overflow.
>
> arbitrary uint32_t + 10 can overflow. Its a defined overflow
> but the following allocation is then bad

I think what happens is arbitrary uint32_t - 24 + 10, which cannot overflow
but it looks like I wasn't convincing.  I assume you want an overflow check?

if (key_buf > UINT32_MAX - pkt_size)
    return AVERROR_INVALIDDATA;

Would this work or do you have a better suggestion?

Regards,
Pavel Roslyy
_______________________________________________
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".

  reply	other threads:[~2025-06-27 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  6:19 Pavel Roslyy
2025-06-24  6:25 ` Pavel Roslyy
2025-06-25 22:12 ` Michael Niedermayer
2025-06-25 22:40   ` Michael Niedermayer
2025-06-26  7:04     ` Pavel Roslyy
2025-06-26 21:08       ` Michael Niedermayer
2025-06-27 19:20         ` Pavel Roslyy [this message]
2025-06-27 21:32           ` Michael Niedermayer
2025-06-26  0:42 ` Andreas Rheinhardt
2025-06-26  7:07   ` Pavel Roslyy

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=CAMM0M58vH6EnJPPJtAXrKvw1Lu5zRWQ0BtOf6YKZ_Hx+TPievA@mail.gmail.com \
    --to=roslypav-at-gmail.com@ffmpeg.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