id3v2 assert failure: *** stack smashing detected ***: id3v2 terminated

Bug #429783 reported by GTMS_OH
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
id3lib
Invalid
Undecided
Unassigned
id3lib3.8.3 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: id3v2

Attempting any file operations (read or write) with id3v2 results in a "stack smashing detected" error. The output for an "id3v2 -l" on a sample file, rather than outputting all id3 tag information and exiting, is as follows:

$ id3v2 -l 01-Fine\ Time.mp3

id3v1 tag info for 01-Fine Time.mp3:
Title : Fine Time Artist: New Order
Album : Technique Year: , Genre: Unknown (255)
Comment: Track: 0
*** stack smashing detected ***: id3v2 terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x40)[0x4adaa0]
/lib/libc.so.6(__fortify_fail+0x0)[0x4ada60]
/usr/lib/libid3-3.8.so.3[0x615d54]
/usr/lib/libid3-3.8.so.3(_ZN7Mp3Info5ParseER10ID3_Readerj+0x8f5)[0x609a05]
/usr/lib/libid3-3.8.so.3(_ZN11ID3_TagImpl11ParseReaderER10ID3_Reader+0x42b)[0x60f0fb]
/usr/lib/libid3-3.8.so.3(_ZN11ID3_TagImpl9ParseFileEv+0x195)[0x60f7e5]
/usr/lib/libid3-3.8.so.3(_ZN11ID3_TagImpl4LinkEPKct+0x54)[0x60b0d4]
/usr/lib/libid3-3.8.so.3(_ZN7ID3_Tag4LinkEPKct+0x2f)[0x60a26f]
id3v2[0x804b39d]
id3v2[0x804c93f]
/lib/libc.so.6(__libc_start_main+0xe6)[0x3e0b56]
id3v2[0x8049751]
======= Memory map: ========
0016a000-0016b000 r-xp 00000000 00:00 0 [vdso]
0016b000-00252000 r-xp 00000000 08:02 674 /usr/lib/libstdc++.so.6.0.13
00252000-00256000 r--p 000e6000 08:02 674 /usr/lib/libstdc++.so.6.0.13
00256000-00257000 rw-p 000ea000 08:02 674 /usr/lib/libstdc++.so.6.0.13
00257000-0025e000 rw-p 00000000 00:00 0
0039e000-003c8000 r-xp 00000000 08:02 54684 /lib/libgcc_s.so.1
003c8000-003c9000 r--p 00029000 08:02 54684 /lib/libgcc_s.so.1
003c9000-003ca000 rw-p 0002a000 08:02 54684 /lib/libgcc_s.so.1
003ca000-0051f000 r-xp 00000000 08:02 65556 /lib/libc-2.10.1.so
0051f000-00520000 ---p 00155000 08:02 65556 /lib/libc-2.10.1.so
00520000-00522000 r--p 00155000 08:02 65556 /lib/libc-2.10.1.so
00522000-00523000 rw-p 00157000 08:02 65556 /lib/libc-2.10.1.so
00523000-00526000 rw-p 00000000 00:00 0
005eb000-0061f000 r-xp 00000000 08:02 15997 /usr/lib/libid3-3.8.so.3.0.0
0061f000-00620000 r--p 00034000 08:02 15997 /usr/lib/libid3-3.8.so.3.0.0
00620000-00622000 rw-p 00035000 08:02 15997 /usr/lib/libid3-3.8.so.3.0.0
009d4000-009f1000 r-xp 00000000 08:02 65553 /lib/ld-2.10.1.so
009f1000-009f2000 r--p 0001c000 08:02 65553 /lib/ld-2.10.1.so
009f2000-009f3000 rw-p 0001d000 08:02 65553 /lib/ld-2.10.1.so
00a5e000-00a72000 r-xp 00000000 08:02 1287 /lib/libz.so.1.2.3.3
00a72000-00a73000 r--p 00013000 08:02 1287 /lib/libz.so.1.2.3.3
00a73000-00a74000 rw-p 00014000 08:02 1287 /lib/libz.so.1.2.3.3
00d12000-00d39000 r-xp 00000000 08:02 65560 /lib/libm-2.10.1.so
00d39000-00d3a000 r--p 00026000 08:02 65560 /lib/libm-2.10.1.so
00d3a000-00d3b000 rw-p 00027000 08:02 65560 /lib/libm-2.10.1.so
08048000-08051000 r-xp 00000000 08:02 31841 /usr/bin/id3v2
08051000-08052000 r--p 00008000 08:02 31841 /usr/bin/id3v2
08052000-08053000 rw-p 00009000 08:02 31841 /usr/bin/id3v2
08d7b000-08d9c000 rw-p 00000000 00:00 0 [heap]
b804d000-b8050000 rw-p 00000000 00:00 0
b8060000-b8062000 rw-p 00000000 00:00 0
bfe1d000-bfe32000 rw-p 00000000 00:00 0 [stack]
Aborted (core dumped)

This occurred in a fully updated Kubuntu karmic alpha 5 installation. id3v2 version information is as follows:

id3v2:
  Installed: 0.1.11-4
  Candidate: 0.1.11-4
  Version table:
 *** 0.1.11-4 0
        500 http://us.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
AssertionMessage: *** stack smashing detected ***: id3v2 terminated
CrashCounter: 1
Date: Mon Sep 14 21:57:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/id3v2
Package: id3v2 0.1.11-4
ProcCmdline: id3v2 -l 01-The\ Nerve.mp3
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-10.32-genusername
Signal: 6
SourcePackage: id3v2
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 __fortify_fail () from /lib/libc.so.6
 __stack_chk_fail () from /lib/libc.so.6
Title: id3v2 assert failure: *** stack smashing detected ***: id3v2 terminated
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
GTMS_OH (ericstockwell04) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
?? () from /lib/libc.so.6
__fortify_fail () from /lib/libc.so.6
__stack_chk_fail () from /lib/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in id3v2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Kyle Cronan (kyle-pbx) wrote :

I think this must originate in id3lib because the same thing happens with the program id3tag from libid3-3.8.3-dev.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 444466, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

affects: id3v2 (Ubuntu) → id3lib3.8.3 (Ubuntu)
Changed in id3lib3.8.3 (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in id3lib3.8.3 (Ubuntu):
status: Confirmed → Invalid
Changed in id3lib:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.