Date: Fri, 7 Oct 2005 08:58:49 -0700 From: David Kirchner <dpk@dpk.net> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-questions@freebsd.org, John Conover <conover@rahul.net> Subject: Re: Security risk associated with a NIC's promiscuous mode? Message-ID: <35c231bf0510070858l32d5aefft4bb9e8508b6b80f@mail.gmail.com> In-Reply-To: <43467C12.1060001@mac.com> References: <20051007084807.13455.qmail@rahul.net> <43467C12.1060001@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/7/05, Chuck Swiger <cswiger@mac.com> wrote: > A mild one. For example, I believe there was recently a security bug in > tcpdump's string handling which could be exploited by tcpdump seeing a > maliciously-crafted packet. Running the NIC in promisc mode means that p= acket > just has to go by, rather than being sent specificly to the machine runni= ng the > sniffer... > > In other words, it's not a great idea to run a sniffer on your most impor= tant > fileserver or whatever, rather than an isolated laptop or other test syst= em. You can also change the ownership of the bpf0 entry in /dev to something other than root, and run tcpdump as that user. Obviously you would want to secure that account so it can only be accessed by you, and you may even want to change ownership to that user only when you want to sniff, changing it back to root when done. In any case, this would mitigate the risk in case a tcpdump/libpcap vulnerability is discovered. I wouldn't do this if it was for a daemon or a cron, though, since they would perform dumps at specific (IE predictable) times of day.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35c231bf0510070858l32d5aefft4bb9e8508b6b80f>