Ubuntu
xfburn package

xfburn crashed with SIGSEGV in GIIO_fwrite()

Bug #1623170 reported by Steven Thomas Greeran on 2016-09-13

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xfburn (Ubuntu)	New	Medium	Unassigned

Bug Description

loaded automatically I didn't even run it??

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: xfburn 0.5.4-1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Mon Sep 12 19:34:04 2016
ExecutablePath: /usr/bin/xfburn
InstallationDate: Installed on 2016-05-07 (129 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcCmdline: xfburn
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: xfburn
StacktraceTop:
__GI__IO_fwrite (buf=0x55e88986d510, size=1, count=40, fp=0x0) at iofwrite.c:37
?? ()
?? ()
__libc_start_main (main=0x55e88984d010, argc=1, argv=0x7fff14980988, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff14980978) at ../csu/libc-start.c:291
?? ()
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
Title: xfburn crashed with SIGSEGV in __GI__IO_fwrite()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Steven Thomas Greeran (sgreeran) wrote on 2016-09-13:

#1

Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (70.6 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (62.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (907 bytes, text/plain; charset="utf-8")
Registers.txt Edit (694 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (209 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (956 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2016-09-13:

#2

StacktraceTop:
__GI__IO_fwrite (buf=buf@entry=0x55e88986d510, size=size@entry=1, count=count@entry=40, fp=fp@entry=0x0) at iofwrite.c:37
fprintf (__fmt=0x55e88986d510 "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\n", __stream=0x0) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
save_settings (priv=0x55e88b10b900) at xfburn-settings.c:191
xfburn_settings_flush () at xfburn-settings.c:366
main (argc=1, argv=0x7fff14980988) at xfburn-main.c:416

Revision history for this message

Apport retracing service (apport) wrote on 2016-09-13: Stacktrace.txt

#3

Stacktrace.txt Edit (835 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-09-13: StacktraceSource.txt

#4

StacktraceSource.txt Edit (1.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-09-13: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (1.5 KiB, text/plain)

Changed in xfburn (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Tyler Hicks (tyhicks) wrote on 2016-09-15:

#6

Hi Steven - Thanks for reporting this bug!

The xfburn code isn't checking the return value of fopen() before using it. fopen() is failing here, returning NULL, and then NULL is passed as the stream to fprintf() resulting in the segfault.

I don't see this as being a security issue so I'm going to open this bug up.

information type:

Private Security → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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