From: Pavel Koshevoy <pkoshevoy@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: Fix get_eia608_packet c608 caption reformatting
Date: Thu, 13 Feb 2025 10:56:59 -0700
Message-ID: <CAJgjuozFZoze6kRqOHPdGxyKwNwoT5kyok4Vd3qU3QSRXFe9QA@mail.gmail.com> (raw)
In-Reply-To: <DU0P250MB074777F3E2502764CEC3F1248FFF2@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM>
On Wed, Feb 12, 2025 at 11:47 PM Andreas Rheinhardt <
andreas.rheinhardt@outlook.com> wrote:
> Pavel Koshevoy:
> > ---
> > libavformat/mov.c | 40 +++++++++++++++++++++++++++++++---------
> > 1 file changed, 31 insertions(+), 9 deletions(-)
> >
> > diff --git a/libavformat/mov.c b/libavformat/mov.c
> > index 85aef33b19..422e515fe8 100644
> > --- a/libavformat/mov.c
> > +++ b/libavformat/mov.c
> > @@ -10790,22 +10790,44 @@ static int mov_change_extradata(AVStream *st,
> AVPacket *pkt)
> >
> > static int get_eia608_packet(AVIOContext *pb, AVPacket *pkt, int size)
> > {
> > - int new_size, ret;
> > -
> > + /* We can't make assumptions about the structure of the payload,
> > + because it may include multiple cdat and cdt2 samples. */
> > + int ret, out_size = 0;
> > if (size <= 8)
> > return AVERROR_INVALIDDATA;
> > - new_size = ((size - 8) / 2) * 3;
> > - ret = av_new_packet(pkt, new_size);
> > +
> > + /* Allocate 3 times the required buffer size to give us enough space
> > + to store the original c608 packet and (potentially 3/2 times
> larger)
> > + reformatted data, safely. */
> > + ret = av_new_packet(pkt, size * 3);
> > if (ret < 0)
> > return ret;
> >
> > - avio_skip(pb, 8);
> > - for (int j = 0; j < new_size; j += 3) {
> > - pkt->data[j] = 0xFC;
> > - pkt->data[j+1] = avio_r8(pb);
> > - pkt->data[j+2] = avio_r8(pb);
> > + /* Load the original c608 payload into the last 3rd of the buffer.
> */
> > + if (avio_read(pb, pkt->data + size * 2, size) != size)
> > + return AVERROR_EOF;
> > +
> > + /* parse and re-format the c608 payload in one pass */
> > + for (uint8_t *out = pkt->data, *src = out + size * 2, *end = src +
> size; src + 8 <= end; ) {
> > + uint32_t atom_size = AV_RB32(src);
> > + uint8_t cc_field =
> > + memcmp(src + 4, "cdat", 4) == 0 ? 1 :
> > + memcmp(src + 4, "cdt2", 4) == 0 ? 2 :
> > + 0;
> > +
> > + if (cc_field != 0) {
> > + for (uint8_t *cc = src + 8, *cc_end = src + atom_size; cc <
> cc_end; cc += 2) {
> > + out[0] = (0x1F << 3) | (1 << 2) | (cc_field - 1);
> > + out[1] = cc[0];
> > + out[2] = cc[1];
> > + out_size += 3;
> > + out += 3;
> > + }
> > + }
> > + src += atom_size;
> > }
> >
> > + pkt->size = out_size;
> > return 0;
> > }
> >
>
> 1. You are trusting atom_size, although it may be insanely large. This
> may lead to segfaults.
> 2. 3 * size might overflow.
> 3. You overallocate a lot here. Wouldn't it be enough to allocate size +
> size / 2? You would then read into pkt->data + size / 2 and reformat the
> data from the start.
> 4. You need to shrink the packet to zero the padding.
> 5. You don't need to keep track of out_size; you can get it via out -
> pkt->data.
>
>
Thank you, I've submitted a 2nd version of the patch that performs more
input validation.
Pavel.
_______________________________________________
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-02-13 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 0:09 Pavel Koshevoy
2025-02-13 2:23 ` Pavel Koshevoy
2025-02-13 6:46 ` Andreas Rheinhardt
2025-02-13 17:56 ` Pavel Koshevoy [this message]
2025-02-13 19:01 ` Devin Heitmueller
2025-02-13 19:59 ` Pavel Koshevoy
2025-02-13 20:12 ` Devin Heitmueller
2025-02-13 21:05 ` Pavel Koshevoy
2025-02-13 22:03 ` Devin Heitmueller
2025-02-13 22:35 ` Pavel Koshevoy
2025-02-13 22:53 ` Pavel Koshevoy
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=CAJgjuozFZoze6kRqOHPdGxyKwNwoT5kyok4Vd3qU3QSRXFe9QA@mail.gmail.com \
--to=pkoshevoy@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