Wireshark mailing list archives
Re: Wireshark 1.6.7 Memory Corruption
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Mon, 20 May 2013 16:10:36 +0200
Hi,This seems to be bug 7744, for which a fix was created for the 1.8 branch upwards. I'm currently not able to say why, but this fix seems not backported to the 1.6 branch AFAIKT.
Thanks, Jaap On May 17, 2013, at 2:01 PM, gobejishvili wrote:
Hello,I'm Security Researcher, found memory corruption vulnerability in Wireshark 1.6.7 version 64BIT, vulnerability detect to kubuntu x64. Drag and drop can to make memory corruption.After running it in GDB. Program received signal SIGSEGV, Segmentation fault. 0x000055555568527f in dnd_open_file_cmd () ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Wireshark 1.6.7 Memory Corruption gobejishvili (May 17)
- Re: Wireshark 1.6.7 Memory Corruption Jaap Keuter (May 20)