Wireshark-bugs: [Wireshark-bugs] [Bug 10038] New: Use of ssl_keys triggers wmem_alloc: assertion
Date: Thu, 24 Apr 2014 23:13:05 +0000
Bug ID 10038
Summary Use of ssl_keys triggers wmem_alloc: assertion failed: (allocator->in_scope)
Classification Unclassified
Product Wireshark
Version Git
Hardware x86
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter lekensteyn@gmail.com

Created attachment 12726 [details]
ca.p12 as used for ssl_keys

Build Information:
v1.11.4-rc1-131-ge209668
--
Upon starting wireshark with ssl_keys added, it crashes with:

   ERROR:epan/wmem/wmem_core.c:49:wmem_alloc: assertion failed:
(allocator->in_scope)

Reproduced with empty profile, and tried variations of .wireshark/ssl_keys

    "any","0","http","ca.p12","passwd"
(also tried "127.0.0.1","443","http","ca.p12","passwd"

The example ca.p12 is attached. Just run "wireshark" with ca.p12 in $PWD
and ssl_keys in ~/.wireshark/ (no other files needed).

Program received signal SIGABRT, Aborted.
0x00007fffe3f48389 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007fffe3f48389 in raise () from /usr/lib/libc.so.6
#1  0x00007fffe3f49788 in abort () from /usr/lib/libc.so.6
#2  0x00007ffff4bb1ef5 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#3  0x00007ffff4bb1f8a in g_assertion_message_expr () from
/usr/lib/libglib-2.0.so.0
#4  0x00007fffe90d921d in wmem_alloc (allocator=0x600e0003faa0, size=54) at
epan/wmem/wmem_core.c:49
#5  0x00007fffe90e23af in wmem_strdup_vprintf (allocator=0x600e0003faa0,
fmt=0x7fffed333e40 "Can not decrypt private key - %s", ap=0x7fffffffd4f0) at
epan/wmem/wmem_strutl.c:92
#6  0x00007fffe90e22db in wmem_strdup_printf (allocator=0x600e0003faa0,
fmt=0x7fffed333e40 "Can not decrypt private key - %s") at
epan/wmem/wmem_strutl.c:75
#7  0x00007fffe9de3afe in ssl_load_pkcs12 (fp=0x6036001731c0,
cert_passwd=0x60040029ddb0 "passwd", err=0x7fffffffd8b0) at
epan/dissectors/packet-ssl-utils.c:3611
#8  0x00007fffe9de9c36 in ssldecrypt_uat_fld_password_chk_cb (r=0x60080010ac90,
p=0x60040029ddb0 "passwd", len=6, u1=0x0, u2=0x0, err=0x7fffffffd990) at
epan/dissectors/packet-ssl-utils.c:4733
#9  0x00007fffe9095839 in uat_load_lex () at epan/uat_load.l:249
#10 0x00007fffe90994f4 in uat_load (uat_in=0x601e0000a360, errx=0x7fffffffda70)
at epan/uat_load.l:327
#11 0x00007fffe9078962 in uat_load_all () at epan/uat.c:449
#12 0x00007fffe8fefe69 in init_prefs () at epan/prefs.c:2855
#13 0x00007fffe8ff29f6 in read_prefs (gpf_errno_return=0x7fffffffdb80,
gpf_read_errno_return=0x7fffffffdbc0, gpf_path_return=0x7fffffffde00,
pf_errno_return=0x7fffffffdd80, pf_read_errno_return=0x7fffffffddc0,
    pf_path_return=0x7fffffffde40) at epan/prefs.c:3174
#14 0x000000000047b324 in read_configuration_files (gdp_path=0x7fffffffe110,
dp_path=0x7fffffffe150) at ui/gtk/main.c:1973
#15 0x000000000047c1b5 in main (argc=1, argv=0x7fffffffe408) at
ui/gtk/main.c:2570


You are receiving this mail because:
  • You are watching all bug changes.