A web shell is a malicious script used by an attacker with the intent to escalate and maintain persistent access on an already compromised web application. A web shell itself cannot attack or exploit a remote vulnerability, so it is always the second step of an attack (this stage is also referred to as post-exploitation).
An attacker can take advantage of common web page vulnerabilities such as SQL injection, remote file inclusion (RFI), or even use cross-site scripting (XSS) as part of a social engineering attack in order to attain file upload capabilities and transfer the malicious files. The common functionality includes but is not limited to shell command execution (access to cmd/command line), code execution, database enumeration, and file management.
Web shells could be written in many web languages, for example, PHP web shells are very common. They can affect you no matter whether your system is based on custom software or on a common content management system such as WordPress with plugins. Web shells might also not get detected by antivirus or anti-malware software because they do not use typical executable file types. At the same time, they are easily available to the public, for example, via several GitHub projects.
In this short series, we want to explain to you in detail how web shells work (using an example of a PHP shell) and how you can detect web shells and protect your assets.
Persistent Remote Access
A web shell script usually contains a backdoor, which allows an attacker to remotely access and possibly control an Internet-facing server at any time. This would save the attacker the inconvenience of having to exploit a vulnerability each time that access to the compromised server is required.
An attacker might also choose to fix the vulnerability themselves in order to ensure that no one else will exploit that vulnerability. This way the attacker can keep a low profile and avoid any interaction with an administrator, while still obtaining the same result.
It is also worth mentioning that several popular web shells use password authentication and other techniques to ensure that only the attacker uploading the web shell has access to it. Such techniques include locking down the script to a specific custom HTTP header, specific cookie values, specific IP addresses, or a combination of these techniques. Most web shells also contain code to identify and block search engines from listing the shell and, as a consequence, blacklisting the entire domain or server that the web application is hosted on – in other words, obfuscation and stealth are key.
Unless a server is misconfigured, the web shell will be running with web server software user permissions, which are (or, at least, should be) limited. Using a web shell, an attacker can attempt to perform privilege escalation attacks by exploiting local vulnerabilities on the system in order to assume root privileges, which, in Linux and other UNIX-based operating systems is the superuser.
With access to the root account, the attacker can essentially do anything on the system including managing local files, installing software, changing permissions, adding and removing users, stealing passwords, reading emails and more.
Pivoting and Launching Attacks
A web shell can be used for pivoting inside or outside a network. The attacker might want to monitor (sniff) the network traffic on the system, scan the internal network to discover live hosts and enumerate firewalls and routers within the network.
This process can take days, even months, predominantly because an attacker typically seeks to keep a low profile and draw the least amount of attention possible. Once an attacker has persistent access, they can patiently make their moves.
The compromised system can also be used to attack or scan targets that reside outside the network. This adds an additional layer of anonymity for the attacker since they are using a 3rd party system to launch an attack. A step further would be to pivot (tunnel) through multiple systems to make it almost impossible to trace an attack back to its source.
Another use of web shells is to make servers part of a botnet. A botnet is a network of compromised systems that an attacker would control, either to use themselves or to lease to other criminals. The web shell or backdoor is connected to a command and control (C&C) server from which it can take commands on what instructions to execute.
This setup is commonly used in distributed denial of service (DDoS) attacks, which require expansive amounts of bandwidth. In this case, the attacker does not have any interest in harming or stealing anything from the system upon which the web shell was deployed. Instead, they will simply use its resources.
An Introduction to Web Shells
Web Shells 101 Using PHP
Keeping Web Shells Under Cover
Web Shells in Action
Detection & Prevention
Frequently asked questions
A web shell is a type of web server malware. It is a script uploaded to your web server by an attacker and executed there. The term shell is used to describe a user interface that you use to access services offered by the operating system.
Web shells are not attacks. Web shells are tools that can be used after a successful attack. If an attacker can upload a file to your server and then run it, they will usually use a web shell. Then, they can continue the attack by running more commands on your web server.
You can discover web shells manually by regularly analyzing web server logs and files. If you suspect that there is a web shell on your web server, you should filter logs for common keywords used by web shells. Also, monitor network for unusual network traffic and connections (outgoing from your server).
The only efficient way to avoid web shells is to eliminate vulnerabilities that let attackers upload web shells. To eliminate vulnerabilities, you must first find them. For that, you need to use a professional vulnerability scanner like Acunetix, which will not only find vulnerabilities but also tell you how to eliminate them.
Get the latest content on web security
in your inbox each week.