netdev - Bug in IPv4 version of ping...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <18429.78.154.109.125.1391423507.squirrel@yellowside.org.uk>
Date:	Mon, 3 Feb 2014 10:31:47 -0000 (GMT)
From:	"Vic" <kernel@...r.org.uk>
To:	netdev@...r.kernel.org
Subject: Bug in IPv4 version of ping...

Hi All.

I hope this is the right place to post this - this list is mentioned as
the mailing list for iputils.

I believe I've found a bug in ping.c - there is an ancient work-around for
an IP_RECVERR bug in raw sockets. The problem is as follows :-

ping_common.c defines a variable working_recverr
ping.c uses this variable to work out what it should do under certain
failure circumstances.

As far as I can see, working_recverr is undefined when first used; the
initial response to it could be either way. This leads to an erroneous
report that the kernel is "not very fresh", and needs to be upgraded.

I have seen this in the current builds for RHEL5 and 6 (s20071127) and in
the current release (s20121221).

I suspect this variable should be set somewhere after option parsing...

HTH

Vic.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html