There‘s an issue where if Deadwood gets a crappy answers from a delegation nameserver, it takes one second to clear it

[samboy]

There’s an issue where if Deadwood gets a crappy answer from a delegation nameserver, instead of immediately clearing the request from Deadwood’s list of pending requests, the request remains a pending request for timeout_seconds seconds (default: 1 second)

This makes it slightly easier to overload Deadwood, however, I would hardly consider it a security bug.

Keep in mind that I wrote that code 16 years ago, I actively maintained the code for about a decade (and I was not paid for either work), but, at this point, I only fix really critical security bugs, and “it’s slightly easier to overload Deadwood than it should be” is not a critical bug for a recursive nameserver which is mainly either for home router use or as a loopback resolver to put on localhost for people who want a local cache. Also, Deadwood’s default configuration is as a caching, not fully recursive, nameserver.