PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-01-02 12:59:02 +00:00
Code Issues Projects Releases Wiki Activity

When using pcap_set_filter() on Linux, valgrind complains about a

Browse Source 
setsockopt() call that uses a pointer to some uninitialized memory. The
error message is the following:

==22214== Syscall param socketcall.setsockopt(optval) points to
uninitialised byte(s)
==22214==    at 0x62F774A: setsockopt (syscall-template.S:82)
==22214==    by 0x4E33B85: ??? (in /usr/lib/libpcap.so.1.0.0)
==22214==    by 0x4E33D0D: ??? (in /usr/lib/libpcap.so.1.0.0)
==22214==    by 0x432253: nsock_pcap_set_filter (in /usr/local/bin/nping)
==22214==    by 0x432557: nsock_pcap_open (in /usr/local/bin/nping)
==22214==    by 0x4295FF: ProbeMode::start() (in /usr/local/bin/nping)
==22214==    by 0x40B2E1: main (in /usr/local/bin/nping)

This patch adds a simple memset() call that makes the warning dissapear.
This commit is contained in:
luis
2010-09-22 09:41:06 +00:00
parent 2be2722f26
commit faaca263b9
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
libpcap/pcap-linux.c
View File

@@ -2148,6 +2148,7 @@ pcap_setfilter_linux_common(pcap_t *handle, struct bpf_program *filter,
struct sock_fprog fcode;
int can_filter_in_kernel;
int err = 0;
memset(&fcode, 0, sizeof(struct sock_fprog));
#endif
if (!handle)