Vulnerabilities / Threats

2/16/2018
10:30 AM
Derek Manky
Derek Manky
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Rise of the 'Hivenet': Botnets That Think for Themselves

These intelligent botnet clusters swarm compromised devices to identify and assault different attack vectors all at once.

Over the past few years, a new development has occurred: predictive software systems are being programmed using artificial intelligence techniques. The latest advances in these kinds of tools use swarm technology to leverage massive databases of expert knowledge comprised of billions of constantly updated bits of data in order to make accurate predictions.

Now the bad news: this technology has not gone unnoticed by cybercriminals. Recent findings from Fortinet threat researchers reveal that intelligent botnets have repeatedly attacked the Apache Struts framework vulnerability responsible for the Equifax hack. Attackers use automation and intelligent decision trees to exploit proven vulnerabilities.

Worse, what bodes ill for the future is that botnets will evolve into hivenets, a type of attack that is able to leverage peer-based self-learning to target vulnerable systems with minimal supervision. Hivenets are intelligent clusters of compromised devices built around swarm technology to create more-effective attack vectors. Whereas traditional botnets wait for commands from the bot herder, hivenets are able to make decisions independently.

Hivenets will be able to use swarms of compromised devices to identify and assault different attack vectors all at once. As it identifies and compromises more devices, a hivenet would be able to grow exponentially, widening its ability to simultaneously attack multiple victims.

A Recurring Infection
Researchers have also discovered that many organizations experience the same botnet infection multiple times, though it is not entirely clear why this is the case; it could be either that the company did not thoroughly understand the scope of the breach and the botnet went dormant, only to return again after business operations went back to normal, or the company never found the root cause. This allows the botnet to return through the same vulnerability.

Security Best Practices
Organizations using cloud services for online transactions can reduce their risk of exposure to hivenets or botnets by following these basic practices:

  • Inventory authorized/unauthorized devices. This should include the cataloging of authorized and unauthorized assets within your environment, including consumer devices like cellphones and laptops. You have to know what you're protecting.
  • Limit user privileges: Not everyone needs administrator privileges.
  • Limit applications in your environment: Use only those with a business need, and keep those applications and systems up to date and fully patched. Using unnecessary applications expands the attack surface and increases the complexity of protecting the environment. Larger enterprises would do well to follow these recommendations, too.
  • Good cyber hygiene: In addition to remaining vigilant about new threats and vulnerabilities in the wild, make sure you don't lose sight of what's happening within your own environment. Network hygiene and device hygiene are perhaps the most neglected elements of security today. Continually removing unnecessary services, stamping out vulnerabilities, and maintaining good order isn't the most fun or sexy part of security, but it is a critically important part.

Related Content:

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Derek Manky formulates security strategy with more than 15 years of cyber security experience behind him. His ultimate goal to make a positive impact in the global war on cybercrime. Manky provides thought leadership to industry, and has presented research and strategy ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Why CISOs Need a Security Reality Check
Joel Fulton, Chief Information Security Officer for Splunk,  6/13/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12557
PUBLISHED: 2018-06-19
An issue was discovered in Zuul 3.x before 3.1.0. If nodes become offline during the build, the no_log attribute of a task is ignored. If the unreachable error occurred in a task used with a loop variable (e.g., with_items), the contents of the loop items would be printed in the console. This could ...
CVE-2018-12559
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. The mount target path check in mounter.cpp `mpOk()` is insufficient. A regular user can consequently mount a CIFS filesystem anywhere (e.g., outside of the /home directory tree) by passing directory traversal sequ...
CVE-2018-12560
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. Arbitrary unmounts can be performed by regular users via directory traversal sequences such as a home/../sys/kernel substring.
CVE-2018-12561
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. A regular user can inject additional mount options such as file_mode= by manipulating (for example) the domain parameter of the samba URL.
CVE-2018-12562
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. The wrapper script 'mount.cifs.wrapper' uses the shell to forward the arguments to the actual mount.cifs binary. The shell evaluates wildcards (such as in an injected string:/home/../tmp/* string).