Sören Tempel 498e531e2f dhcpv6: don't treat zero option as an end-of-payload marker ... As far as I can tell, no DHCPv6 RFC specifies this option. The handling for the zero option was added in #17736 by @benpicco to fix issues encountered while trying to retrieve a DHCHPv6 lease. However, I strongly suspect that the zero option was encountered in this case due to an out-of-bounds read performed in RIOT's DHCPv6 client implementation (i.e. the option parsing loop read beyond the packet bounds). This issue was fixed in #18307 and I strongly suspect that it should also fix the issue @benpicco originally encountered in #17736. As such, I propose that we remove the if statement which treats the zero option as an end-of-payload marker. Fixes #18309		2022-09-22 20:08:00 +02:00
..
_dhcpv6.h	doc: fix unbalaced grouping	2022-09-14 15:05:25 +02:00
client_dns.c	dhcpv6_client: add DNS recursive name server option handling	2021-06-24 16:01:59 +02:00
client.c	dhcpv6: don't treat zero option as an end-of-payload marker	2022-09-22 20:08:00 +02:00
Kconfig	Merge pull request #16228 from JKRhb/dhcp-ia-na	2021-08-11 20:50:01 +02:00
Makefile	dhcpv6: provide initial client implementation	2020-01-16 12:36:03 +01:00
relay.c	dhcpv6_relay: initial import of a lightweight DHCPv6 relay agent	2021-08-11 13:19:06 +02:00