Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/usmdec: add support for HCA stream decryption
Date: Thu, 26 Jun 2025 23:08:07 +0200
Message-ID: <20250626210807.GF29660@pb2> (raw)
In-Reply-To: <CAMM0M59gS8oHhy6jXa9v2-tZ7VbMz8_5e2ThBATD_cG4P2q33A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]

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

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".

  reply	other threads:[~2025-06-26 21:08 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 [this message]
2025-06-27 19:20         ` Pavel Roslyy
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=20250626210807.GF29660@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