You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened: When sending an AXFR request over UDP (which typical clients like dig prevents you from doing), CoreDNS will happily reply over UDP, which has the potential of generating big payloads and used as an amplification vector.
What you expected to happen: AXFR to be limited in size and force TC or possibly return NOTIMPL (like root AXFR server do for instance)
How to reproduce it (as minimally and precisely as possible):
Return refused when the query comes in over udp.
No need to add a new test case as the current crop needed to be changed
to use TCP.
Fixes: #4450
Signed-off-by: Miek Gieben <[email protected]>
* plugin/transfer: only allow outgoing axfr over tcp
Return refused when the query comes in over udp.
No need to add a new test case as the current crop needed to be changed
to use TCP.
Fixes: #4450
Signed-off-by: Miek Gieben <[email protected]>
* transfer tests: this needs tcp as well
Signed-off-by: Miek Gieben <[email protected]>
What happened: When sending an AXFR request over UDP (which typical clients like
dig
prevents you from doing), CoreDNS will happily reply over UDP, which has the potential of generating big payloads and used as an amplification vector.What you expected to happen: AXFR to be limited in size and force TC or possibly return NOTIMPL (like root AXFR server do for instance)
How to reproduce it (as minimally and precisely as possible):
Using a modified miekg/exdns 's q.o
Running:
With a Corefile:
using the modified q.go:
we can see that CoreDNS would reply to the AXFR request over UDP.
Anything else we need to know?:
Environment:
cat /etc/os-release
):Ubuntu 20.10
The text was updated successfully, but these errors were encountered: