Bug 879798

Summary: [abrt] wget-1.14-3.fc18: sk_value: Process /usr/bin/wget was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: wgetAssignee: Tomáš Hozza <thozza>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: micah, thozza, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:121d059e23b035bfb995b2d3986779a6ecc18052
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 08:52:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Jan Teichmann 2012-11-24 14:20:31 UTC 
Version-Release number of selected component:
wget-1.14-3.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/bin/wget '--header=Content-Type: multipart/form-data; boundary=--------------------------4a1c55cf63ecfea6' --post-file=/tmp/chromium-upload-22235e9a6125103d https://clients2.google.com/cr/report --timeout=10 --tries=1 -O /dev/fd/3
crash_function: sk_value
kernel:         3.6.7-5.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 sk_value at stack.c:303
: #1 x509_name_encode at x_name.c:266
: #2 x509_name_ex_i2d at x_name.c:229
: #3 ASN1_item_ex_i2d at tasn_enc.c:181
: #4 asn1_item_flags_i2d at tasn_enc.c:122
: #5 ASN1_item_i2d at tasn_enc.c:91
: #6 i2d_X509_NAME at x_name.c:129
: #7 X509_NAME_cmp at x509_cmp.c:199
: #8 OBJ_bsearch_ex_ at obj_dat.c:700
: #9 internal_find at stack.c:229
Comment 1 Jan Teichmann 2012-11-24 14:20:34 UTC 
Created attachment 650980 [details]
File: core_backtrace
Comment 2 Jan Teichmann 2012-11-24 14:20:42 UTC 
Created attachment 650981 [details]
File: environ
Comment 3 Jan Teichmann 2012-11-24 14:20:44 UTC 
Created attachment 650982 [details]
File: limits
Comment 4 Jan Teichmann 2012-11-24 14:20:47 UTC 
Created attachment 650983 [details]
File: backtrace
Comment 5 Jan Teichmann 2012-11-24 14:20:49 UTC 
Created attachment 650984 [details]
File: cgroup
Comment 6 Jan Teichmann 2012-11-24 14:20:51 UTC 
Created attachment 650985 [details]
File: executable
Comment 7 Jan Teichmann 2012-11-24 14:20:54 UTC 
Created attachment 650986 [details]
File: maps
Comment 8 Jan Teichmann 2012-11-24 14:20:56 UTC 
Created attachment 650987 [details]
File: dso_list
Comment 9 Jan Teichmann 2012-11-24 14:20:58 UTC 
Created attachment 650988 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2012-11-24 14:21:00 UTC 
Created attachment 650989 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2012-11-24 14:21:02 UTC 
Created attachment 650990 [details]
File: open_fds
Comment 12 Tomáš Hozza 2012-11-26 08:05:15 UTC 
To me it looks more like a bug in OpenSSL library. Changing component to openssl.
Comment 13 Tomas Mraz 2012-11-26 10:29:00 UTC 
Can you reproduce this bug with regular wget call to https:// URL? I think this is some kind of memory corruption before the OpenSSL is called. The reason is the backtrace is from OpenSSL initialization and if the bug was really there basically anything that uses OpenSSL for SSL calls would be broken.
Comment 14 Jan Teichmann 2012-11-26 11:08:01 UTC 
OpenSSL works fine and I couldn't reproduce the bug with wget https URLs

This bug occurred when the google chrome browser tried to upload a crash report to google.
Comment 15 Tomas Mraz 2013-01-09 11:36:38 UTC 
*** Bug 892993 has been marked as a duplicate of this bug. ***
Comment 16 Tomas Mraz 2013-01-09 11:38:51 UTC 
Back to wget as I believe this is not a bug in OpenSSL but rather some incorrect call of OpenSSL from wget or memory corruption from wget.
Comment 17 Jan Teichmann 2013-01-10 08:52:04 UTC 
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.