#413555 libtag1c2a: id3v2 zero-sized frame parsing

Package:
libtag1c2a
Source:
taglib
Submitter:
Lehel Bernadt
Date:
2026-07-29 17:13:02 UTC
Severity:
important
Tags:
#413555#5
Date:
2007-03-05 19:44:33 UTC
From:
To:
I have many mp3 files which have id3v2 tags with zero-sized frames in
them; that is, the 4 byte frame identfier, 4 nulls, and 2 flag bytes.
This isn't an issue with other tag processing apps/libs, but taglib
fails to parse the tag after such a frame. So only the data to the first
such frame is processed, which leads to an incomplete display of file
information in the various players using taglib.
The attached patch fixes the issue.

#413555#20
Date:
2026-07-29 16:44:13 UTC
From:
To:
On Mon, 05 Mar 2007 20:44:33 +0100 Lehel Bernadt <lehel@pmc-services.hu> wrote:
 > Package: libtag1c2a
 > Version: 1.4-4
 > Severity: important
 > Tags: patch
 >
 >
 > I have many mp3 files which have id3v2 tags with zero-sized frames in
 > them; that is, the 4 byte frame identfier, 4 nulls, and 2 flag bytes.
 > This isn't an issue with other tag processing apps/libs, but taglib
 > fails to parse the tag after such a frame. So only the data to the first
 > such frame is processed, which leads to an incomplete display of file
 > information in the various players using taglib.
 > The attached patch fixes the issue.
 >
 > -- System Information:
 > Debian Release: 4.0
 > APT prefers unstable
 > APT policy: (500, 'unstable')
 > Architecture: i386 (i686)
 > Shell: /bin/sh linked to /bin/bash
 > Kernel: Linux 2.6.18-ck1
 > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 >
 > Versions of packages libtag1c2a depends on:
 > hi libc6 2.3.6-7 GNU C Library: Shared libraries
 > hi libgcc1 1:4.1.1-21 GCC support library
 > hi libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
 > hi zlib1g 1:1.2.3-11 compression library - runtime
 >
 > libtag1c2a recommends no packages.
 >
 > -- no debconf information

I believe this issue has been fixed since https://github.com/taglib/taglib/issues/512 .
As a result, I am closing this bug report accordingly.

Nevertheless, my analysis could be incorrect. If you find out that this bug is actually
not fixed, please feel free to open a new bug report against current Debian releases,
or even better, work with upstream to solve the bug at upstream issue tracker.

Best Regards,
Boyuan Yang