Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

2/8/2011
07:28 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Tracking The Botnet's DNS Trail

Combining domain-flux detection with DNS query-failure graphing could help pinpoint the wiliest botnets

A researcher is looking at mapping trends in Domain Name System (DNS) queries to better pinpoint stealthy botnet activity and ultimately the botnet's command and control (C&C) infrastructure.

Zhi-Li Zhang, a professor at the University of Minnesota, is looking at new methods for detecting botnets that try to hide behind alternating domain names in what's called DNS domain-fluxing -- also known as domain generation algorithm (DGA). In domain-fluxing, the bot queries a series of domain names, but the domain owner registers just one. The Conficker, Kraken, and Torpig botnets all use this method of evasion.

To get to the C&C for these types of botnets, researchers typically have to reverse-engineer the bot malware and then figure out the domains that are generated regularly in order to register them as a way to infiltrate the botnet. But that process is time-consuming and resource-intensive, researchers say.

Zhang recently came up with a way to graph failed DNS queries in order to root out these types of botnets. "The basic idea of our approach is to observe and analyze DNS failures to identify and pinpoint domain-flux botnets, which tend to generate a large amount of failed DNS queries," Zhang says. He and his research team basically map all of the failed DNS queries and then extract the most dominant subgraphs, he says.

But there are some challenges to this approach. "The key challenges here are that there might be a variety of reasons that DNS queries may fail, so how can we identify failures that are likely caused by bots? And there may exist multiple botnets, [so] is it possible for us to identify bots that belong to each botnet or similar class of botnets?" Zhang says.

The next phase of his research, which is currently in its preliminary stages, is to be able to detect botnets in near real-time by using machine learning and before signatures are developed for characterizing the botnets. Zhang will be using his method of mapping DNS query failures, coupled with an existing method of DNS fast-flux detection that looks at the pattern and distribution of alphabetic characters in a domain name to determine whether it's malicious or legitimate: This allows them to spot botnets' algorithmically generated (rather than generated by humans) domain names. Given that most domain names are already taken, botnet operators have to go with gibberish-looking names like Conficker does: joftvvtvmx.org, gcvwknnxz.biz, and vddxnvzqjks.ws, which their bots generate.

The hope is that a combination of these two methods of spotting irregular DNS traffic for gathering botnet clues will provide even more powerful detection capabilities. Then DNS could be used to peek at relevant HTTP traffic, for instance. DNS is often the first step for bots to find their C&C server -- once they do, they use HTTP to communicate with it, according to Zhang. First inspecting the DNS traffic flows for botnet activity saves a lot of time and effort because HTTP traffic overall is so prolific and parsing it is so unwieldy, he says.

A copy of Zhang's work on DNS failure graphing is available here (PDF).

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
Preventing PTSD and Burnout for Cybersecurity Professionals
Craig Hinkley, CEO, WhiteHat Security,  9/16/2019
NetCAT Vulnerability Is Out of the Bag
Dark Reading Staff 9/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3738
PUBLISHED: 2019-09-18
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Improper Verification of Cryptographic Signature vulnerability. A malicious remote attacker could potentially exploit this vulnerability to coerce two parties into computing the same predictable shared key.
CVE-2019-3739
PUBLISHED: 2019-09-18
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to Information Exposure Through Timing Discrepancy vulnerabilities during ECDSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover ECDSA keys.
CVE-2019-3740
PUBLISHED: 2019-09-18
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover DSA keys.
CVE-2019-3756
PUBLISHED: 2019-09-18
RSA Archer, versions prior to 6.6 P3 (6.6.0.3), contain an information disclosure vulnerability. Information relating to the backend database gets disclosed to low-privileged RSA Archer users' UI under certain error conditions.
CVE-2019-3758
PUBLISHED: 2019-09-18
RSA Archer, versions prior to 6.6 P2 (6.6.0.2), contain an improper authentication vulnerability. The vulnerability allows sysadmins to create user accounts with insufficient credentials. Unauthenticated attackers could gain unauthorized access to the system using those accounts.