Skip Menu |
Report information
The Basics
Id: 48804
Status: open
Priority: 50/50
Queue: dhcp-public

Bug Information
Version Fixed: (no value)
Version Found: (no value)
Versions Affected: (no value)
Versions Planned: (no value)
Priority: (no value)
Severity: (no value)
CVSS Score: (no value)
CVE ID: (no value)
Component: (no value)
Area: (no value)

Dates
Created:Mon, 14 Jan 2019 07:14:49 -0500
Updated:Mon, 14 Jan 2019 09:34:03 -0500
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

From: "Radek Zajic" <radek@zajic.v.pytli.cz>
Date: Mon, 14 Jan 2019 12:14:38 +0000
To: dhcp-bugs@isc.org
Subject: any, with libraries containing fix for RT #46709 - isc-dhcp crashes when running in DHCPv6 mode
Download (untitled) / with headers
text/plain 1.2KiB
Bug Report from www.isc.org: Name: Radek Zajic Email: radek@zajic.v.pytli.cz Software Version: any, with libraries containing fix for RT #46709 OS: Linux Subject:isc-dhcp crashes when running in DHCPv6 mode Bug Detail =========== As described on https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699 (and the linked bugs), there is an issue within ISC DHCP. This issue did not directly manifest itself until a bug was fixed in BIND libraries (RT #46709), which are used in ISC DHCP too. When ISC DHCP is compiled with the respective libraries (https://gitlab.isc.org/wpk/bind9/commit/65a483106e45704e19781bfe4f4634db4f77562e), the server crashes when running in DHCPv6 mode. It appears so that the DHCPv6 code somehow tries to delete a heap entry that has been already deleted. This results in failed assertion in the library code, followed by application backtrace. In the bug report on Ubuntu site, I have also posted a quick-and-dirty patch. This patch checks the heap index and if it is nonzero, it does not call the isc_heap_delete function. This obviously does not resolve the root cause, only avoids the crashes. Could you kindly check if this can be fixed - and if yes, provide a patch? Thank you very much. Kind regards, Radek Zajic --- This email was received through isc.org Bug Submission Form
Hello Radek: This issue was corrected in ISC DHCP 4.4.1 under rt46719. ISC DHCP 4.3.* is EOL at this point. I have attached a patch that should work 4.3.6 but keep in mind that it does not represent an official, tested patch. Our official response for your issue is to suggest you upgrade 4.4.1. Upgrading from 4.3.5 to 4.4.1 should be painless, they are architecturally compatible. Speaking of EOL, 4.4.1 is the last feature release of ISC DHCP as we are putting our focus on new DHCP product: https://www.isc.org/kea While we do plan on doing some maintenance releases for ISC DHCP, the next one (4.4.2) has not yet been scheduled. It might be a good time for you to look into migrating to Kea. Thank you for your inquiry, I help this addresses the issue for you. Sincerely, Thomas Markwalder ISC Software Engineering
Subject: Re: [ISC-Bugs #48804] any, with libraries containing fix for RT #46709 - isc-dhcp crashes when running in DHCPv6 mode
Date: Mon, 14 Jan 2019 14:18:09 +0000
To: "dhcp-public@isc.org" <dhcp-public@isc.org>
From: "Radek Zajíc" <radek@zajic.v.pytli.cz>
Hi Thomas, Thank you for your prompt response. Unfortunately the attachment seems to be missing in this e-mail message. Would you mind rechecking if it has been sent or not? (I do not have access to the bugreport on https://bugs.isc.org/Public/Ticket/Display.html?id=48804 so cannot check if the file is there.) As for Kea, I have already tried (and somehow succeeded) in migrating of my configuration to Kea, however the JSON config file is a horrible idea. Besides the JSON config file, Kea does not have the powerful conditional logic capabilities of ISC DHCP, which is something I need to perform network boot with different config files/filename paths (legacy boot, UEFI TFTP boot, UEFI HTTP boot, Raspberry Pi network boot, via IPv4 and IPv6). I have somehow managed to hack most of it in, but it's not something I'd call clean and DRY. I definitely support the thinking behind Kea, but am afraid the upgrade path will not be straightforward for many ISC DHCP users. Thank you for your support. Kind regards, Radek Zajic Dne 14.01.19 15:09, Thomas Markwalder via RT <dhcp-public@isc.org> napsal(a): Hello Radek: This issue was corrected in ISC DHCP 4.4.1 under rt46719. ISC DHCP 4.3.* is EOL at this point. I have attached a patch that should work 4.3.6 but keep in mind that it does not represent an official, tested patch. Our official response for your issue is to suggest you upgrade 4.4.1. Upgrading from 4.3.5 to 4.4.1 should be painless, they are architecturally compatible. Speaking of EOL, 4.4.1 is the last feature release of ISC DHCP as we are putting our focus on new DHCP product: https://www.isc.org/kea While we do plan on doing some maintenance releases for ISC DHCP, the next one (4.4.2) has not yet been scheduled. It might be a good time for you to look into migrating to Kea. Thank you for your inquiry, I help this addresses the issue for you. Sincerely, Thomas Markwalder ISC Software Engineering
From: "Thomas Markwalder" <tmark@isc.org>
To: dhcp-public@isc.org
Date: Mon, 14 Jan 2019 09:33:58 -0500
Subject: Re: [ISC-Bugs #48804] any, with libraries containing fix for RT #46709 - isc-dhcp crashes when running in DHCPv6 mode
Download (untitled) / with headers
text/plain 2.4KiB
Hello Radek Apparently the patch was attached only to the reply within RT. Let me try that again, hopefully you'll find it attached to this email. Thanks for your feedback on what stumbling blocks you found with Kea so far.  We'll take them into account as we look for ways to improve upon it. Sincerely, Thomas Markwalder On 1/14/19 9:18 AM, Radek Zajic via RT wrote: > Hi Thomas, > > Thank you for your prompt response. Unfortunately the attachment seems to be missing in this e-mail message. Would you mind rechecking if it has been sent or not? (I do not have access to the bugreport on https://bugs.isc.org/Public/Ticket/Display.html?id=48804 so cannot check if the file is there.) > > As for Kea, I have already tried (and somehow succeeded) in migrating of my configuration to Kea, however the JSON config file is a horrible idea. Besides the JSON config file, Kea does not have the powerful conditional logic capabilities of ISC DHCP, which is something I need to perform network boot with different config files/filename paths (legacy boot, UEFI TFTP boot, UEFI HTTP boot, Raspberry Pi network boot, via IPv4 and IPv6). I have somehow managed to hack most of it in, but it's not something I'd call clean and DRY. > > I definitely support the thinking behind Kea, but am afraid the upgrade path will not be straightforward for many ISC DHCP users. > > Thank you for your support. > > Kind regards, > Radek Zajic > > Dne 14.01.19 15:09, Thomas Markwalder via RT <dhcp-public@isc.org> napsal(a): > > Hello Radek: > > This issue was corrected in ISC DHCP 4.4.1 under rt46719. ISC DHCP 4.3.* is EOL at this point. I have attached a patch that should work 4.3.6 but keep in mind that it does not represent an official, tested patch. Our official response for your issue is to suggest you upgrade 4.4.1. Upgrading from 4.3.5 to 4.4.1 should be painless, they are architecturally compatible. > > Speaking of EOL, 4.4.1 is the last feature release of ISC DHCP as we are putting our focus on new DHCP product: > > https://www.isc.org/kea > > While we do plan on doing some maintenance releases for ISC DHCP, the next one (4.4.2) has not yet been scheduled. It might be a good time for you to look into migrating to Kea. > > Thank you for your inquiry, I help this addresses the issue for you. > > Sincerely, > > Thomas Markwalder > ISC Software Engineering > > > >
Download 46719.v4_3.diff
text/x-patch 7.5KiB

Message body is not shown because sender requested not to inline it.