Re: Is bind 9.18.19 a validating resolver to shield against CVE-2023-42119 ?

2023-10-03 Thread Rob van der Putten via bind-users
Hi there On 02/10/2023 11:06, Kurt Jaeger wrote: In the light of the recent exim security issues[1,2] I'm trying to find out if bind 9.18.19, if used as resolver, does enough validation to shield exim instances from CVE-2023-42119 ? I added 'check-names response fail;' to the internal view.

Re: Is bind 9.18.19 a validating resolver to shield against CVE-2023-42119 ?

2023-10-03 Thread Petr Menšík
Hi Kurt, we do not ship exim in RHEL, so nobody from our team did proper work on these vulnerabilities. From the few information that I have found, I would just guess BIND9 or Unbound should help protecting exim. Dnsmasq or coredns do not create full response message from scratch, but forward

Re: Is bind 9.18.19 a validating resolver to shield against CVE-2023-42119 ?

2023-10-02 Thread Petr Špaček
On 02. 10. 23 11:06, Kurt Jaeger wrote: Hi! In the light of the recent exim security issues[1,2] I'm trying to find out if bind 9.18.19, if used as resolver, does enough validation to shield exim instances from CVE-2023-42119 ? As details and reproducers for the CVE are not available, this is

Is bind 9.18.19 a validating resolver to shield against CVE-2023-42119 ?

2023-10-02 Thread Kurt Jaeger
Hi! In the light of the recent exim security issues[1,2] I'm trying to find out if bind 9.18.19, if used as resolver, does enough validation to shield exim instances from CVE-2023-42119 ? As details and reproducers for the CVE are not available, this is a more general question. Pointers on where