Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/imfdec: check track valid before use it
Date: Fri, 26 Aug 2022 10:37:41 +0200
Message-ID: <DB6PR0101MB221496FB0DF6034305C656C08F759@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20220826064456.92895-1-lq@chinaffmpeg.org>

Steven Liu:
> fix CID: 1512414
> And return AVERROR_INVALIDDATA when get_next_track_with_minimum_timestamp
> incorrect in imf_read_packet;
> 
> Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
> ---
>  libavformat/imfdec.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/libavformat/imfdec.c b/libavformat/imfdec.c
> index 5bbe7a53f8..08f342bc1a 100644
> --- a/libavformat/imfdec.c
> +++ b/libavformat/imfdec.c
> @@ -697,8 +697,9 @@ static IMFVirtualTrackPlaybackCtx *get_next_track_with_minimum_timestamp(AVForma
>          }
>      }
>  
> -    av_log(s, AV_LOG_DEBUG, "Found next track to read: %d (timestamp: %lf / %lf)\n",
> -           track->index, av_q2d(track->current_timestamp), av_q2d(minimum_timestamp));
> +    if (track)
> +        av_log(s, AV_LOG_DEBUG, "Found next track to read: %d (timestamp: %lf / %lf)\n",
> +               track->index, av_q2d(track->current_timestamp), av_q2d(minimum_timestamp));

Coverity actually complained about track being uninitialized, which this
patch does not address. And the reason it does this is that it doesn't
understand the algorithm: track will always be initialized in the first
iteration of the loop. (If there is a first iteration of the loop -- is
this actually guaranteed? A file without tracks seems to be pretty useless.)
FYI: In Coverity's analysis there are loop iterations, but it just
assumed that track is not initialized in the loop (which boils down to
saying that it presumed the tracks' current_timestamp to be invalid
(denominator 0). I hope this can't happen.
(There is btw another issue: The initialization of minimum_timestamp
presumes that int are 32bit which need not be true.)

>      return track;
>  }
>  
> @@ -760,6 +761,8 @@ static int imf_read_packet(AVFormatContext *s, AVPacket *pkt)
>      AVRational next_timestamp;
>  
>      track = get_next_track_with_minimum_timestamp(s);
> +    if (!track)
> +        return AVERROR_INVALIDDATA;
>  
>      ret = get_resource_context_for_timestamp(s, track, &resource);
>      if (ret)

_______________________________________________
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:[~2022-08-26  8:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  2:50 [FFmpeg-devel] [PATCH 1/2] " Steven Liu
2022-08-26  2:50 ` [FFmpeg-devel] [PATCH 2/2] avformat/dashdec: check val before xmlFree it Steven Liu
2022-08-26  3:52 ` [FFmpeg-devel] [PATCH 1/2] avformat/imfdec: check track valid before use it Pierre-Anthony Lemieux
2022-08-26  6:12   ` Steven Liu
2022-08-26  6:44   ` [FFmpeg-devel] [PATCH v2] " Steven Liu
2022-08-26  8:37     ` Andreas Rheinhardt [this message]
2022-08-26 15:44       ` Pierre-Anthony Lemieux
2022-08-26 16:01         ` Andreas Rheinhardt
2022-08-26 16:06           ` Pierre-Anthony Lemieux
2022-08-27 12:25             ` Steven Liu
2022-08-27 17:25               ` Pierre-Anthony Lemieux
2022-09-08 15:21                 ` Pierre-Anthony Lemieux

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=DB6PR0101MB221496FB0DF6034305C656C08F759@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.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