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.

Application Security

2/4/2021
04:45 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Web Application Attacks Grow Reliant on Automated Tools

Attackers often use automation in fuzzing attacks, injection attacks, fake bots, and application DDoS attacks.

Cybercriminals targeting Web applications have grown more reliant on automated tools in their attacks, report Barracuda Networks researchers who analyzed two months of attack data. 

Related Content:

Concerns Over API Security Grow as Attacks Increase

Special Report: Special Report: Understanding Your Cyber Attackers

New From The Edge: What I Wish I Knew at the Start of My InfoSec Career

The top five threat types were dominated by attacks deployed using automated tools, they found. Fuzzing attacks (19.46%) were most prevalent, followed by injection attacks (12.07%), fake bots (12.02%), application distributed denial-of-service (9.29%), and blocked bots (1.2%). 

Automated attacks rely on bots to exploit vulnerabilities in Web applications, and there are two classes of attackers who use them. The larger amount of traffic comes from attackers who don't try to target a specific website but deploy automated attacks at scale. Another, smaller group uses automated tools to target e-commerce websites and other sites to generate a profit. 

These threats may take the form of fake bots posing as Google bots to avoid detection, or they could manifest as app DDoS attacks trying to crash a website by quietly overloading a Web app. Most attack traffic came from fuzzing, or reconnaissance, tools used to probe apps for bugs. 

"You typically use fuzzing attacks as a way to test the applications and find out the bounds of the application, and then you use those results … to go and try to break the application," says Tushar Richabadas, senior product marketing manager of Applications and Cloud Security, and leader of this research. 

An attacker may try to send a large number of parameters in the URL to see how an application behaves, he explains. The app may throw an error and display a page where the attacker can learn it uses a SQL database. Knowing this, they could try a SQL injection attack and see if the app doesn't sanitize something properly, which could help them gain access to the database. 

A fuzzing attack is typically a first step in an attack, Richabadas says. With the knowledge they gain from fuzzing, an attacker can figure out how to move forward. Most attacks researchers observed against JSON APIs were testing boundary conditions, attempting to fuzz the APIs. 

Injection attacks, the second most common type of automated attack, are a known classic Web application threat. Most attackers used automated tools like sqlmap to try and break into apps, and many of these attacks were "script kiddie-level noise," the researchers write in a blog post

This "noise" made up the bulk of attack traffic researchers analyzed, Richabadas points out.

"There [is] a small number of sophisticated attackers going off to specific sites, but they are, to an extent, an exception in the data that we saw," he explains. "The more prevalent are lesser-skilled attackers who are just starting out. … They make up the overwhelming amount of traffic."

These lesser-skilled attackers slowly learn how the threats work; as they persist, they start to become more specialized and go in one of two directions, Richabadas continues. Some become bug bounty hunters and pursue white-hat cybersecurity careers; some go in another direction and pursue cybercrime, where they go into creating attack tools themselves, Richabadas says.

Organizations are getting better at defending against fake bots, the third most common type of automated attack, but these bots are more prevalent today than they were a year ago, he adds. 

"People are definitely waking up to the problems that bots are causing," he says. Most major e-commerce companies, along with airlines and media publications, have begun to invest in bot management solutions. The attackers who employ fake bots likely are after information from a specific site but don't want to be recognized or stopped, so they disguise themselves as a bot.

Application DDoS attacks were "surprisingly prevalent," researchers found. These are different from the more talked-about volumetric DDoS attacks, which are usually intended to bring a site down and easily detectable because of their effects.

"When it comes to an application DDoS attack, it's more subtle," Richabadas explains. "You'll try to find a way to overload the site's resources without being noticed." For example, an attacker will try to download a very large file, very slowly, or try to overload an app's search function. The app doing all these transactions will slow down without a detectable spike in traffic.

Application DDoS attacks aren't as widely known and most applications protect against it, so these incidents are typically targeted, he adds. The researchers couldn't conclude why these attacks saw an increase in this type of threat. 

While automated attacks are not new to the threat landscape, the operators behind them are becoming increasingly diligent, Richabadas says. "Most of this [attack] traffic that we've seen is noise and the signal is actually hidden," he notes. "Attackers are getting more intelligence, and they are bypassing measures by pretending to be almost human, and so on."

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...
CVE-2021-3197
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.