xfstt assert failure: *** buffer overflow detected ***: /usr/bin/xfstt terminated

Bug #433146 reported by samana@swing.be
684
This bug affects 66 people
Affects Status Importance Assigned to Milestone
xfstt (Debian)
Fix Released
Unknown
xfstt (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xfstt

xfstt assert failure: *** buffer overflow detected **

ProblemType: Crash
Architecture: i386
AssertionMessage: *** buffer overflow detected ***: /usr/bin/xfstt terminated
CrashCounter: 1
Date: Sat Sep 19 18:42:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xfstt
Package: xfstt 1.7-5
ProcCmdline: /usr/bin/xfstt --daemon --notcp
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.27-14.35-generic
Signal: 6
SourcePackage: xfstt
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 __fortify_fail () from /lib/tls/i686/cmov/libc.so.6
Title: xfstt assert failure: *** buffer overflow detected ***: /usr/bin/xfstt terminated
Uname: Linux 2.6.27-14-generic i686
UserGroups:

Revision history for this message
samana@swing.be (samana) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
__libc_message (do_abort=2,
*__GI___fortify_fail (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xfstt (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Kees Cook (kees)
visibility: private → public
Changed in xfstt (Ubuntu):
status: New → Confirmed
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

this could be
src/xfstt.cc:
   strncpy(info.magic, "TTFNINFO", 8);

but,
src/xfstt.h:
typedef struct {
        char magic[4]; // == TTFN
        char type[4]; // == INFO or NAME
        u16_t version;
        u16_t key;
        u32_t crc;
        //TTFNdata ttfn[];
} TTFNheader;

so maybe,
src/xfstt.cc:
- strncpy(info.magic, "TTFNINFO", 8);
+ strncpy(info.magic, "TTFN", 4);
+ strncpy(info.type, "INFO", 4);

seems to work, does that look sane? i cant get the failure on debian so i'm not entirely sure whats going on in ubuntu specifically

tags: added: patch
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

having said that a no change rebuild seems to fix it too, the previous patch seems to hold though, if it isnt causing this crash its still a problem. test build ppa below

xfstt (1.7-6ubuntu1~sevenmachines1) lucid; urgency=low

   * src/xfstt.cc:
    - don't copy TTFNINFO into TTFNHeader's magic variable, it should be
    broken into TTFN for magic and INFO for type (LP:#433146)

https://launchpad.net/~sevenmachines/+archive/release+1

Changed in xfstt (Ubuntu):
assignee: nobody → SevenMachines (sevenmachines)
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

sorry, a bit of confusion, a no change rebuild still leaves the crash, the patch is the fix in reality

Changed in xfstt (Ubuntu):
assignee: SevenMachines (sevenmachines) → nobody
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

wish i'd noticed Bug #403074 before :), i'll say a quick thanks to PCC since it is the same fix!

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

i'll report to debian, if its showing up there now it surely will at some point

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

remember to update maintainer

Revision history for this message
Michael Bienia (geser) wrote :

Uploaded to lucid. Thanks for your contribution.

Changed in xfstt (Ubuntu):
status: Confirmed → Fix Released
Changed in xfstt (Debian):
status: Unknown → New
Changed in xfstt (Debian):
status: New → Fix Released
Revision history for this message
rifter (rifter0x0000) wrote :

Okay it says the fix is released, but in what version? I have the latest package and this still continuously happens. Further, the bug continues to exist in Lucid https://bugs.launchpad.net/ubuntu/+source/xfstt/+bug/575026

I see the patch in here, but is it going to get included in a package? I though that was what fix released meant.

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.