DNS Ping Scans via Open Resolvers

Updated

Our last post covered some of the ways that Rumble gathers information from DNS services.

While working on the tracer implementation, we identified a trick that other folks might find it useful. It turns out that most DNS resolvers do not filter the address ranges they will contact when handling a request, allowing for remote subnet "ping scans" with a little work. This technique isn't foolproof, and is probably not new, but it may have interesting security implications.

The Rumble DNS Server #

To support the DNS trace requests used by Rumble, we built a reflective DNS server in Go, based on the Miek Gieben's reflect.go sample. This DNS service will return the resolver address in the response for A and AAAA queries, along with the port number for TXT queries. In addition to the trace request, this service will read EDNS0 Client Subnet information and return the subnet data as an encoded CNAME response. Finally, and most relevant to this post, this service will return a NS response for certain queries as a decoded value of the question. This allows clients to ask the resolving DNS server to contact arbitrary nameservers by address.

DNS Remote Ping Scan #

On the client side, we send a DNS request with a name formatted like the following:

<RANDOM-ID>.<ENCODED-ADDRESS-OF-SCAN-TARGET>.<SUBDOMAIN>.<DOMAIN>.<TLD>

If we send this request to an open resolver with the encoded address of 192.168.0.1, the resolver will ask the Rumble DNS server for the NS record of the encoded subdomain, get a response that resolves to 192.168.0.1, and then send a DNS request to 192.168.0.1 asking for the entire name. This is nothing new and one of the basic features of DNS, but can lead to some surprising results.

Segmented Discovery #

VLAN segmentation is often used to prevent wireless guest users from reaching corporate assets directly, while still allowing these users to query the internal DNS server. This configuration can be abused by our DNS technique to perform a remote ping scan of the corporate network from the guest VLAN. In the example below, the client at 192.168.0.150 can talk to the internet and to the DNS server at 192.168.0.1, but is not allowed to communicate with the retail point of sale subnet 192.168.30.0/24. The client will use the technique outlined in this post to perform a ping scan of the retail subnet through the shared DNS resolver:

$ rumble-dnsrp -quiet 192.168.0.1 192.168.30.0/24
192.168.30.29              alive via 192.168.0.1:53                60ms       code:2
192.168.30.34              alive via 192.168.0.1:53                69ms       code:2
192.168.30.143             alive via 192.168.0.1:53               267ms       code:2

Private Cloud Subnets #

If the DNS server is hosted in a cloud environment, there is a good chance that this technique can be used to scan the private subnets. The example below demonstrates scanning a remote Amazon VPC using an internet-exposed open resolver:

$ rumble-dnsrp -quiet My.Cloud.DNS.Server 172.31.0.0/24
172.31.0.1                 alive via A.B.C.D:53                    75ms       code:2
172.31.0.2                 alive via A.B.C.D:53                    79ms       code:2
172.31.0.3                 alive via A.B.C.D:53                   165ms       code:2
172.31.0.4                 alive via A.B.C.D:53                    72ms       code:2

Note that the latency of 172.31.0.3 is a bit more than double that of the other hosts; we can infer that this is not only a live system, but one also running an open resolver. This behavior can also be tested by sending a query for the loopback address, which can also result in a double lookup with the expected latency:

$ rumble-dnsrp -quiet My.Cloud.DNS.Server 127.0.0.1
127.0.0.1                  alive via A.B.C.D:53                   160ms       code:2

Testing Connectivity #

This technique also allows us to check the latency between two sites. For example, we can ask the Google DNS servers to scan the Cloudflare subnet:

$ rumble-dnsrp -quiet 8.8.8.8 1.1.1.0/24
1.1.1.1                    alive via 8.8.8.8:53                   166ms       code:2

The reverse works well too:

$ rumble-dnsrp -quiet 1.1.1.1 8.8.8.0/24
8.8.8.8                    alive via 1.1.1.1:53                    56ms       code:2
8.8.8.1                    alive via 1.1.1.1:53                    47ms       code:2

We can also ask public DNS servers to scan random internet subnets for us:

$ rumble-dnsrp -quiet 1.1.1.1 13.89.49.0/24
13.89.49.137               alive via 1.1.1.1:53                    75ms       code:2

Response Criteria #

The previous examples all result in DNS queries being sent from the nameserver to addresses we choose. The tool assumes the target is "alive" if one of the following is true:

  • The target runs a DNS server and replied with an error
  • The target sent back an ICMP unreachable (no DNS service)

If the received error code is not 2 or the request timed out, one of these conditions wasn't met. Error code 5 generally means the nameserver refused to perform our query (its authoritative only, not an open resolver).

Open Source Tools #

If you would like to try this technique, you can grab both the Rumble DNS Server and the DNS Remote Ping utility from the runZero Tools repository. Unless you would like to run your own nameserver, the DNS Remote Ping utility may be all you need, which will use a subdomain hosted by us by default (v1.nxdomain.us). If you have a Go environment configured and the $GOPATH/bin directory in your path, the following command will install the client (rumble-dnsrp):

$ go get github.com/runZeroInc/runzero-tools/cmd/rumble-dnsrp

Moving Forward #

Our goal is to build the best products for IT and security professionals through applied research. We hope that you found this detour into DNS behavior interesting and that you will check out our product, Rumble Network Discovery

Written by HD Moore

HD Moore is the co-founder and CEO of runZero. Previously, he founded the Metasploit Project and served as the main developer of the Metasploit Framework, which is the world's most widely used penetration testing framework.
More about HD Moore
Subscribe Now

Get the latest news and expert insights delivered in your inbox.

Welcome to the club! Your subscription to our newsletter is successful.


Related Articles

runZero Research
SSHamble: Unexpected exposures in the Secure Shell
We conducted a deep dive into the SSH ecosystem and identified vulnerabilities across a wide range of implementations. During the research process,...
runZero Research
Attack Surface Challenges with OT/ICS and Cloud Environments
Learn why successfully navigating changes to operational technology and cloud attack surfaces is critical for successful asset security.
Life at runZero
Employee Spotlight: Nikki Milum
Nikki Milum is our stellar Senior People Operations Partner! Read on to learn more about why Nikki thinks runZero is different than any place she’s...
runZero Research
Evolving threat landscapes: a view through the lens of CAASM
See what our analysis of sample CAASM data reveals about the current threat landscape and how security teams are responding to challenges old and new.

See Results in Minutes

Get complete visibility into IT, OT, & IoT — without agents, credentials, or hardware.

© Copyright 2024 runZero, Inc. All Rights Reserved