 | Senior Member with 414 posts. | | | | Wireshark 1.2.2 - how secure is it? Hi,
Well, this is a general question: I've read that, though Wireshark is considered to be maybe the best packet sniffer out there, it used to have some serious security holes. Ones that could be utilized by hackers to gain control of your machine.
Two questions before I start using it:
1) Is this still the case?
2) If I install it, will the security breaches supposedly introduced by Wireshark be present in my system even when I don't run it?
Thanks,
Daniel.
__________________ No animals were harmed in the making of this steak | | Distinguished Member with 4,901 posts. | | Join Date: Apr 2002 Location: Birmingham, England | | | | | Member with 93 posts. | | Join Date: Dec 2008 Experience: Intermediate | | | | | Distinguished Member with 4,901 posts. | | Join Date: Apr 2002 Location: Birmingham, England | | Software to 'sniff' (or check or test) the content of packets of data passing over a network I think (I didn't check Wikipedia, so that could be completely wrong!).
I only knew about Wireshark because I visit the Internet Storm Center at a site called SANS.org, which is maintained by and for network admins and most of it goes over my head. However, it does occasionally have info of interest to a general home user like myself (such as early warning of the next major exploit).
Here's the Wireshark story as it appeared at Sans org; http://isc.sans.org/diary.html?storyid=7132
__________________ Nothing matters very much, and few things matter at all.
Lord Balfour 1848-1930 | | Senior Member with 414 posts. | | | | As I understand it, all information transferred through the Internet is packed in packets. What Wireshark (and any other packet sniffer) does is read and analyze those packages, without stopping them from reaching their destination. However, in order to do that it requires access to sensitive OS areas, which means that if it has security vulnerabilities/holes, they could be used to do some damage to your system.
TOGG - yeah, I've read the R-notes. But it discusses some specific fixes they've made, doesn't really tell you how secure (or not) it is now.
__________________ No animals were harmed in the making of this steak | | Distinguished Member with 14,988 posts. | | Join Date: Sep 2003 Location: -71.45091, 42.27841 | | Hi BlackHorseman,
Here's a Security excerpt from Wireshark: Quote:
One possible alternative is to run tcpdump, or the dumpcap utility that comes with Wireshark, with superuser privileges to capture packets into a file, and later analyze these packets by running Wireshark with restricted privileges on the packet capture dump file. On wireless networks, it is possible to use the Aircrack wireless security tools to capture IEEE 802.11 frames and read the resulting dump files with Wireshark.
As of Wireshark 0.99.7, Wireshark and tshark run dumpcap to do traffic capture. On platforms where special privileges are needed to capture traffic, only dumpcap needs to be set up to run with those special privileges - neither Wireshark nor tshark need to run with special privileges, and neither of them should be run with special privileges.
| As an aside, I would only run Wireshark as advised above, and then only to inspect an internal network. The latest stable version is 1.2.3 / 2009-10-27.
-- Tom | |
Smart Search
| Find your solution! | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | |  WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.
| You Are Using: |
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 01:33 PM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd. | |
|