From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/dhav: Don't truncate return value of avio_skip()
Date: Mon, 9 May 2022 21:18:32 +0200
Message-ID: <DB6PR0101MB2214BA18521DAD434E26A6DC8FC69@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <AS8PR01MB79445C44D79B226CA80FF4188FC49@AS8PR01MB7944.eurprd01.prod.exchangelabs.com>
Andreas Rheinhardt:
> Fixes demuxing files bigger than INT_MAX.
>
> Reported-by: jenster
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> This has just been reported by jenster on IRC:
>
> <jenster> I found a bug in libavformat/dhav.c where it fails to demux files > INT_MAX. It's basically assigning the result of avio_skip (which returns an int64_t file offset) to an int in two places which it then checks if it's less than 0 and when the file is bigger than INT_MAX it overflows and becomes negative and errors out (this seems like something
> <jenster> that static analysis should find). It's a two line fix (basically just change two ints to int64_t) https://pastebin.com/iUGe9cza (licensed CC0). Would anyone be able to submit this change or fix it their own way? I don't care about credit and I really don't want to bother with the whole patch submission process for this trivial change.
>
> libavformat/dhav.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libavformat/dhav.c b/libavformat/dhav.c
> index 60aab8cabd..9d26efe8fc 100644
> --- a/libavformat/dhav.c
> +++ b/libavformat/dhav.c
> @@ -78,10 +78,11 @@ static const uint32_t sample_rates[] = {
> static int parse_ext(AVFormatContext *s, int length)
> {
> DHAVContext *dhav = s->priv_data;
> - int index, ret = 0;
> + int64_t ret = 0;
>
> while (length > 0) {
> int type = avio_r8(s->pb);
> + int index;
>
> switch (type) {
> case 0x80:
> @@ -168,8 +169,7 @@ static int read_chunk(AVFormatContext *s)
> {
> DHAVContext *dhav = s->priv_data;
> int frame_length, ext_length;
> - int64_t start, end;
> - int ret;
> + int64_t start, end, ret;
>
> if (avio_feof(s->pb))
> return AVERROR_EOF;
Will apply later today unless there are objections.
- Andreas
_______________________________________________
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".
prev parent reply other threads:[~2022-05-09 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 6:29 Andreas Rheinhardt
2022-05-09 19:18 ` Andreas Rheinhardt [this message]
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=DB6PR0101MB2214BA18521DAD434E26A6DC8FC69@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