It was discovered that Unbound incorrectly handled delegations with a large number of non-responsive nameservers. A remote attacker could possibly use this issue to cause Unbound to consume resources, leading to a denial of service.
{ "availability": "No subscription needed", "binaries": [ { "unbound-anchor": "1.13.1-1ubuntu5.3", "python3-unbound": "1.13.1-1ubuntu5.3", "unbound-host": "1.13.1-1ubuntu5.3", "unbound": "1.13.1-1ubuntu5.3", "libunbound8": "1.13.1-1ubuntu5.3", "libunbound-dev": "1.13.1-1ubuntu5.3" } ] }
{ "availability": "No subscription needed", "binaries": [ { "libunbound8": "1.9.4-2ubuntu1.4", "libunbound-dev": "1.9.4-2ubuntu1.4", "unbound-anchor": "1.9.4-2ubuntu1.4", "python3-unbound": "1.9.4-2ubuntu1.4", "python-unbound": "1.9.4-2ubuntu1.4", "unbound-host": "1.9.4-2ubuntu1.4", "unbound": "1.9.4-2ubuntu1.4" } ] }
{ "availability": "No subscription needed", "binaries": [ { "libunbound2": "1.6.7-1ubuntu2.6", "libunbound-dev": "1.6.7-1ubuntu2.6", "unbound-anchor": "1.6.7-1ubuntu2.6", "python3-unbound": "1.6.7-1ubuntu2.6", "python-unbound": "1.6.7-1ubuntu2.6", "unbound-host": "1.6.7-1ubuntu2.6", "unbound": "1.6.7-1ubuntu2.6" } ] }