I've yesterday pinged the security Team as FYI on this.
In the meanwhile by tracking the upstream list this seems to be the follow up fix: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=141a26f979b4bc959d8e866a295e24f8cf456920 With the following being related https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=305cb79c5754d5554729b18a2c06fe7ce699687a
It will fix the immediate issue, but compared to the past the SP will stay the same now, see this discussion. https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q1/014735.html
@Marc/Security - are you going to follow on on those CVE pushes with that fix or do we need a different plan of action?
I've yesterday pinged the security Team as FYI on this.
In the meanwhile by tracking the upstream list this seems to be the follow up fix: /thekelleys. org.uk/ gitweb/ ?p=dnsmasq. git;a=commit; h=141a26f979b4b c959d8e866a295e 24f8cf456920 /thekelleys. org.uk/ gitweb/ ?p=dnsmasq. git;a=commit; h=305cb79c5754d 5554729b18a2c06 fe7ce699687a
https:/
With the following being related
https:/
It will fix the immediate issue, but compared to the past the SP will stay the same now, see this discussion. /lists. thekelleys. org.uk/ pipermail/ dnsmasq- discuss/ 2021q1/ 014735. html
https:/
@Marc/Security - are you going to follow on on those CVE pushes with that fix or do we need a different plan of action?