From: hassanhany via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: hassanhany <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] avcodec/vorbisdec: validate windowtype and transformtype (PR #21547)
Date: Thu, 22 Jan 2026 14:25:43 -0000
Message-ID: <176909194370.25.5439127286555311890@4457048688e7> (raw)
PR #21547 opened by hassanhany
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21547
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21547.patch
validates the windowtype and transformtype as required by the Vorbis spec in section 4.2.4 the part about modes "verify ranges; zero is the only legal value in Vorbis I for [vorbis_mode_windowtype] and [vorbis_mode_transformtype]."
>From bcfd563e25adb1e818b309018b7c03b684668751 Mon Sep 17 00:00:00 2001
From: Hassan Hany <hassanhanyrashad@gmail.com>
Date: Thu, 22 Jan 2026 15:31:41 +0200
Subject: [PATCH] avcodec/vorbisdec: validate windowtype and transformtype
---
libavcodec/vorbisdec.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/libavcodec/vorbisdec.c b/libavcodec/vorbisdec.c
index 60a83f394f..1bfebda101 100644
--- a/libavcodec/vorbisdec.c
+++ b/libavcodec/vorbisdec.c
@@ -908,8 +908,14 @@ static int vorbis_parse_setup_hdr_modes(vorbis_context *vc)
vorbis_mode *mode_setup = &vc->modes[i];
mode_setup->blockflag = get_bits1(gb);
- mode_setup->windowtype = get_bits(gb, 16); //FIXME check
- mode_setup->transformtype = get_bits(gb, 16); //FIXME check
+ mode_setup->windowtype = get_bits(gb, 16);
+ mode_setup->transformtype = get_bits(gb, 16);
+ if (mode_setup->transformtype != 0 || mode_setup->windowtype != 0) {
+ av_log(vc->avctx, AV_LOG_ERROR,
+ "Invalid mode: windowtype %u, transformtype %u (both must be 0)\n",
+ mode_setup->windowtype, mode_setup->transformtype);
+ return AVERROR_INVALIDDATA;
+ }
GET_VALIDATED_INDEX(mode_setup->mapping, 8, vc->mapping_count);
ff_dlog(NULL, " %u mode: blockflag %d, windowtype %d, transformtype %d, mapping %d\n",
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-01-22 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176909194370.25.5439127286555311890@4457048688e7 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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