After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703307 - Segfault in excel_read_BOUNDSHEET on a corrupted (fuzzed) xls file
Segfault in excel_read_BOUNDSHEET on a corrupted (fuzzed) xls file
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export MS Excel (tm)
git master
Other Linux
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-06-29 11:20 UTC by jutaky
Modified: 2013-06-30 15:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jutaky 2013-06-29 11:20:15 UTC
Segfault in excel_read_BOUNDSHEET on a corrupted (fuzzed) xls file.

Git versions of glib, goffice, gnumeric, libgsf and libxml2.

Test case: http://jutaky.com/fuzzing/gnumeric_case_30057_29410.xls

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe6b3b372 in excel_read_BOUNDSHEET (q=0x7ca650, importer=0x7c8160) at ms-excel-read.c:1497
1497			bs->streamStartPos = GSF_LE_GET_GUINT32 (q->non_decrypted_data);
(gdb) bt
  • #0 excel_read_BOUNDSHEET
    at ms-excel-read.c line 1497
  • #1 excel_read_workbook
    at ms-excel-read.c line 7091
  • #2 excel_enc_file_open
    at boot.c line 193
  • #3 excel_file_open
    at boot.c line 250
  • #4 go_plugin_loader_module_func_file_open
    at app/go-plugin-loader-module.c line 282
  • #5 go_plugin_file_opener_open
    at app/go-plugin-service.c line 685
  • #6 go_file_opener_open
    at app/file.c line 417
  • #7 workbook_view_new_from_input
    at workbook-view.c line 1272
  • #8 workbook_view_new_from_uri
    at workbook-view.c line 1332
  • #9 main
    at main-application.c line 321

--
Juha Kylmänen
Research Assistant, OUSPG
Comment 1 Morten Welinder 2013-06-30 15:24:54 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.