Segmentation fault /opt/xplico/bin/mfbc #1047

Closed
bugcrash opened this Issue Dec 22, 2016 · 7 comments

Projects

None yet

3 participants

@bugcrash

bugcrash@seconion:/opt/xplico/bin$ ./mfbc
mfbc v1.1.1
Internet Traffic Decoder (NFAT).
See http://www.xplico.org for more information.

Copyright 2007-2014 Gianluca Costa & Andrea de Franceschi and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This product includes GeoLite data created by MaxMind, available from http://www.maxmind.com/.

usage: ./mfbc [-h] [-s] [-l] [-i] [-c <config_file>] -p
-c config file
-s silent
-p connection port
-i info (PEI generated by this manipulator)
-l print all log in the screen
-h this help
NOTE: parameters MUST respect this order!

bugcrash@seconion:/opt/xplico/bin$ gdb -q /opt/xplico/bin/mfbc
Reading symbols from /opt/xplico/bin/mfbc...(no debugging symbols found)...done.
(gdb) r -c ruby -e 'puts "A" * 9024'
Starting program: /opt/xplico/bin/mfbc -c ruby -e 'puts "A" * 9024'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
mfbc v1.1.1
Internet Traffic Decoder (NFAT).
See http://www.xplico.org for more information.

Copyright 2007-2014 Gianluca Costa & Andrea de Franceschi and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This product includes GeoLite data created by MaxMind, available from http://www.maxmind.com/.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7425943 in _IO_vfprintf_internal (s=, format=,
ap=ap@entry=0x7fffffffbf18) at vfprintf.c:1661
1661 vfprintf.c: No such file or directory.
(gdb) i r rdi
rdi 0x4141414141414141 4702111234474983745

@dougburks
Contributor

Hi @bugcrash ,

Are you trying to report an issue within Xplico itself? If so, please submit it to the Xplico developers directly.

Per the Xplico wiki:

"Don't hesitate to report bugs to bug[@]xplico.org and/or use the forum."
http://wiki.xplico.org/doku.php?id=xplico

Thanks!

@bugcrash

@dougburks
Because securityonion is using the code. Why wait for the third party to fix the issue.

@dougburks
Contributor

I've submitted this to bug@xplico.org on your behalf.

@dougburks
Contributor

No response yet from bug@xplico.org, so I've also posted this to:
http://forum.xplico.org/viewtopic.php?f=4&t=572

@dougburks
Contributor

Still no response from bug@xplico.org or http://forum.xplico.org/viewtopic.php?f=4&t=572, so I've emailed Gianluca Costa personally.

@dougburks dougburks closed this Jan 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment