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 577399 - Null pointer crash in excel_read_CF
Null pointer crash in excel_read_CF
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export MS Excel (tm)
git master
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-03-31 06:15 UTC by sum1
Modified: 2009-03-31 13:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fuzzed xls file (11.50 KB, application/vnd.ms-excel)
2009-03-31 06:16 UTC, sum1
Details

Description sum1 2009-03-31 06:15:21 UTC
Version: r17258
OS: Ubuntu Intrepid

The upcoming file is a fuzzed version of the .xls document from http://qa.openoffice.org/issues/show_bug.cgi?id=2130.


Steps to reproduce:
- Import the upcoming attachment to trigger a crash


Backtrace:

Program received signal SIGSEGV, Segmentation fault.

Thread 3067479808 (LWP 17451)

  • #0 excel_read_CF
    at ms-excel-read.c line 4777
  • #1 excel_read_CONDFMT
    at ms-excel-read.c line 5006
  • #2 excel_read_sheet
    at ms-excel-read.c line 6303
  • #3 excel_read_BOF
    at ms-excel-read.c line 6552
  • #4 excel_read_workbook
    at ms-excel-read.c line 6635
  • #5 excel_file_open
    at boot.c line 192
  • #6 go_plugin_loader_module_func_file_open
    at go-plugin-loader-module.c line 239
  • #7 go_plugin_file_opener_open
    at go-plugin-service.c line 476
  • #8 go_file_opener_open
    at file.c line 299
  • #9 wb_view_new_from_input
    at workbook-view.c line 1058
  • #10 wb_view_new_from_uri
    at workbook-view.c line 1112
  • #11 main
    at main-application.c line 413

Comment 1 sum1 2009-03-31 06:16:25 UTC
Created attachment 131751 [details]
fuzzed xls file
Comment 2 Morten Welinder 2009-03-31 13:12:45 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.