From: Baptiste Coudurier via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Baptiste Coudurier <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] lavf/id3v2: allow empty strings without bom, fixes #20597 (PR #20778)
Date: Tue, 28 Oct 2025 18:02:07 -0000
Message-ID: <176167452850.81.1291318136500672648@7d278768979e> (raw)
PR #20778 opened by Baptiste Coudurier (bcoudurier)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20778
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20778.patch
>From 1025beeef1d7a46340378f7297ae1399f12d9b99 Mon Sep 17 00:00:00 2001
From: Baptiste Coudurier <baptiste.coudurier@gmail.com>
Date: Tue, 28 Oct 2025 10:59:01 -0700
Subject: [PATCH] lavf/id3v2: allow empty strings without bom, fixes #20597
---
libavformat/id3v2.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/libavformat/id3v2.c b/libavformat/id3v2.c
index 21a5d2fbf6..3ce2fadce8 100644
--- a/libavformat/id3v2.c
+++ b/libavformat/id3v2.c
@@ -268,7 +268,7 @@ static int decode_str(AVFormatContext *s, AVIOContext *pb, int encoding,
case ID3v2_ENCODING_UTF16BOM:
if ((left -= 2) < 0) {
- av_log(s, AV_LOG_ERROR, "Cannot read BOM value, input too short\n");
+ av_log(s, AV_LOG_ERROR, "Cannot read BOM value, input too short %d\n", left);
ffio_free_dyn_buf(&dynbuf);
*dst = NULL;
return AVERROR_INVALIDDATA;
@@ -279,6 +279,11 @@ static int decode_str(AVFormatContext *s, AVIOContext *pb, int encoding,
get = avio_rl16;
case 0xfeff:
break;
+ case 0: // empty string without bom
+ ffio_free_dyn_buf(&dynbuf);
+ *dst = NULL;
+ *maxread = left;
+ return 0;
default:
av_log(s, AV_LOG_ERROR, "Incorrect BOM value: 0x%x\n", bom);
ffio_free_dyn_buf(&dynbuf);
--
2.49.1
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-10-28 18:02 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=176167452850.81.1291318136500672648@7d278768979e \
--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