Package: dhcp3-server
Version: 3.0.4-14

I'm filling a new bug report because the one already describing the
problem has been archived. (#334980)

The problem has indeed not been fixed. It can be demonstrated with
either the configuration file I'm attaching, or the one already
provided in #334980. I did all my tests and fixes with the
configuration file I'm attaching. It shows that it can be even more
malicious than expected as a simple typo in last statement of a pool
can trigger it (there should be  "unknown-clients" with a final 's'
instead of "unknown-client" in the last pool)

Answer of Andrew Pollock <apollock@debian.org> to #334980 dated Fri, 21
Oct 2005 19:27:41 +1000 is not a solution to this bug because dhcpd3
tests its configuration file using the very same parser it uses to
parse its configuration file during normal startup, and the endless
loop filling syslogs is within the parser, so the problem also occurs
during the consistency check.

The problem is in a do {} while () loop in parse_pool_statement that
does not tests for end of file conditions.

I attach a patch that fixes the bug, that I'll send upstream to.

Hello,

This bug was reported to Debian, with a patch. The bug reporter said that
they were also going to send the patch directly upstream, but as of 3.1.0, I
see no evidence of the patch being applied, so I'm sending this upstream.

Please maintain the Cc line to keep our bug tracking system in the loop.

regards

Andrew

----- Forwarded message from Guillaume Knispel <gknispel@proformatique.com> -----

From: Guillaume Knispel <gknispel@proformatique.com>
To: submit@bugs.debian.org
Subject: Bug#430772: dhcp3-server goes into infinite loop and fill syslog
 if started with this bad configuration file
Date: Wed, 27 Jun 2007 11:26:40 +0200
Organization: Proformatique
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; i486-pc-linux-gnu)

Package: dhcp3-server
Version: 3.0.4-14

I'm filling a new bug report because the one already describing the
problem has been archived. (#334980)

The problem has indeed not been fixed. It can be demonstrated with
either the configuration file I'm attaching, or the one already
provided in #334980. I did all my tests and fixes with the
configuration file I'm attaching. It shows that it can be even more
malicious than expected as a simple typo in last statement of a pool
can trigger it (there should be  "unknown-clients" with a final 's'
instead of "unknown-client" in the last pool)

Answer of Andrew Pollock <apollock@debian.org> to #334980 dated Fri, 21
Oct 2005 19:27:41 +1000 is not a solution to this bug because dhcpd3
tests its configuration file using the very same parser it uses to
parse its configuration file during normal startup, and the endless
loop filling syslogs is within the parser, so the problem also occurs
during the consistency check.

The problem is in a do {} while () loop in parse_pool_statement that
does not tests for end of file conditions.

I attach a patch that fixes the bug, that I'll send upstream to.
-- 
Guillaume KNISPEL
Proformatique - 67 rue Voltaire - 92800 Puteaux
Tel. : 01 41 38 99 60 - Fax. : 01 41 38 99 70
gknispel@proformatique.com - http://www.proformatique.com/

----- End forwarded message -----

Dear submitter,

as the package isc-dhcp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1143544

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)