Attack and vulnerability types¶

The Wallarm filtering node can detect many attacks and vulnerabilities. These attacks and vulnerabilities are listed below.

Each entity in the list

• Is tagged with either Attack, Vulnerability, or both.

  The name of a particular attack can be the same as the name of the vulnerability this attack exploits. In this case, such an entity will be tagged with the combined Vulnerability/Attack tag.

• Has the Wallarm code that corresponds to this entity.

Most of the vulnerabilities and attacks on this list are also accompanied by one or more codes from the list of software weakness types, also known as the Common Weakness Enumeration or CWE.

Additionally, the Wallarm filtering node employs several special attack and vulnerability types for the internal purpose of marking processed traffic. Such entities are not accompanied by CWE codes but are listed separately.

The main list of attacks and vulnerabilities¶

Attack on XML External Entity (XXE)¶

Vulnerability/Attack

CWE code: CWE-611

Wallarm code: xxe

Description:

The XXE vulnerability allows an attacker to inject an external entity in an XML document to be evaluated by an XML parser and then executed on the target web server.

As the result of a successful attack, an attacker will be able to:

• Get access to the web application's confidential data

• Scan internal data networks

• Read the files located on the web server

• Perform an SSRF attack

• Perform a Denial of Service (DoS) attack

This vulnerability occurs due to a lack of restriction on the parsing of XML external entities in a web application.

Remediation:

You may follow these recommendations:

• Disable the parsing of XML external entities when working with the XML documents supplied by a user.

• Apply the recommendations from the OWASP XXE Prevention Cheat Sheet.

Brute-force attack¶

Attack

CWE codes: CWE-307, CWE-521, CWE-799

Wallarm code: brute

Description:

A brute-force attack occurs when a massive number of requests with a predefined payload are sent to the server. These payloads may be generated by some means or taken from a dictionary. The server's response is then analyzed to find the right combination of the data in the payload.

A successful brute‑force attack can potentially bypass authentication and authorization mechanisms and/or reveal a web application's hidden resources (such as directories, files, website parts, etc.), thus granting the ability to conduct other malicious actions.

Remediation:

You may follow these recommendations:

• Limit the number of requests per a certain time period for a web application.

• Limit the number of authentication/authorization attempts per a certain time period for a web application.

• Block new authentication/authorization attempts after a certain number of the failed attempts.

• Restrict a web application from accessing any files or directories on the server it runs on, except those within the scope of the application.

How to configure the Wallarm solution to protect applications from brute force →

Resource scanning¶

Attack

CWE code: none

Wallarm code: scanner

Description:

The scanner code is assigned to an HTTP request if this request is believed to be part of third‑party scanner software activity that is targeted to attack or scan a protected resource. The Wallarm Scanner's requests are not considered to be a resource scanning attack. This information may be used later to attack these services.

Remediation:

You may follow these recommendations:

• Limit the possibility of a network perimeter scan by employing IP address allowlisting and denylisting along with authentication/authorization mechanisms.

• Minimize the scan surface by placing the network perimeter behind a firewall.

• Define a necessary and sufficient set of ports to be opened for your services to operate.

• Restrict the usage of ICMP protocol on the network level.

• Periodically update your IT infrastructure equipment. This includes:

  • firmware of servers and other equipment
  • operating systems
  • other software

Server‑Side Template Injection (SSTI)¶

Vulnerability/Attack

CWE codes: CWE-94, CWE-159

Wallarm code: ssti

Description:

An attacker can inject an executable code into a user‑filled form on a web server vulnerable to SSTI attacks so that code will be parsed and executed by the web server.

A successful attack may render a vulnerable web server completely compromised, potentially allowing an attacker to execute arbitrary requests, explore the server's file systems, and, under certain conditions, remotely execute arbitrary code (see RCE attack for details), as well as many other things.

This vulnerability arises from the incorrect validation and parsing of user input.

Remediation:

You may follow the recommendation to sanitize and filter all user input to prevent an entity in the input from being executed.

Data bomb¶

Attack

CWE code: CWE-409, CWE-776

Wallarm code: data_bomb

Description:

Wallarm marks a request as the Data bomb attack if it contains the Zip or XML bomb:

• Zip bomb is a malicious archive file designed to crash or render useless the program or system reading it. Zip bomb allows the program to work as intended, but the archive is crafted so that unpacking it requires inordinate amounts of time, disk space and/or memory.

• XML bomb (billion laughs attack) is the DoS attack type that is aimed at parsers of XML documents. An attacker sends malicious payloads in XML entities.

  For example, entityOne can be defined as 20 entityTwo, which themselves can be defined as 20 entityThree. If the same pattern is continued until entityEight, the XML parser will unfold a single occurrence of entityOne to 1 280 000 000 entityEight — taking up 5 GB of memory.

Remediation:

Limit the size of incoming requests so it could not harm the system.

Cross‑site scripting (XSS)¶

Vulnerability/Attack

CWE code: CWE-79

Wallarm code: xss

Description:

A cross‑site scripting attack allows an attacker to execute a prepared arbitrary code in a user's browser.

There are a few XSS attack types:

• Stored XSS is when a malicious code is pre‑embedded in the web application's page.

  If the web application is vulnerable to the stored XSS attack, then it is possible for an attacker to inject a malicious code into the web application's HTML page; moreover, this code will persist and be executed by the browser of any user who requests the infected webpage.

• Reflected XSS is when an attacker tricks a user into opening a specially crafted link.

• DOM‑based XSS is when a JavaScript code snippet built into the web application's page parses the input and executes it as a JavaScript command due to errors in this code snippet.

Exploiting any of the vulnerabilities listed above leads to the execution of an arbitrary JavaScript code. Provided that the XSS attack was successful, an attacker may steal a user's session or credentials, make requests on behalf of the user, and perform other malicious actions.

This class of vulnerabilities occurs due to the incorrect validation and parsing of user input.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• While forming the web application's pages, sanitize and escape any entities that are formed dynamically.

• Apply the recommendations from the OWASP XSS Prevention Cheat Sheet.

Broken Object Level Authorization (BOLA)¶

Vulnerability/Attack

CWE code: CWE-639

Wallarm code: idor for vulnerabilities, bola for attacks

Description:

Attackers can exploit API endpoints that are vulnerable to broken object level authorization by manipulating the ID of an object that is sent within the request. This may lead to unauthorized access to sensitive data.

This issue is extremely common in API-based applications because the server component usually does not fully track the client’s state, and instead, relies more on parameters like object IDs, that are sent from the client to decide which objects to access.

Depending on the API endpoint logic, an attacker can either just read data on web applications, APIs and users or modify them.

This vulnerability is also known as IDOR (Insecure Direct Object Reference).

More details on the vulnerability

Remediation:

• Implement a proper authorization mechanism that relies on the user policies and hierarchy.

• Prefer to use random and unpredictable values as GUIDs for objects' IDs.

• Write tests to evaluate the authorization mechanism. Do not deploy vulnerable changes that break the tests.

Wallarm behavior:

• Wallarm automatically discovers vulnerabilities of this type.

• Wallarm does not detect attacks exploiting this vulnerability by default. To detect and block the BOLA attacks, configure the BOLA trigger.

Open redirect¶

Attack

CWE code: CWE-601

Wallarm code: redir

Description:

An attacker can use an open redirect attack to redirect a user to a malicious web page via a legitimate web application.

Vulnerability to this attack occurs due to incorrect filtering of URL inputs.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• Notify users about all pending redirects, and ask for explicit permission.

Server‑side Request Forgery (SSRF)¶

Vulnerability/Attack

CWE code: CWE-918

Wallarm code: ssrf

Description:

A successful SSRF attack may allow an attacker to make requests on behalf of the attacked web server; this potentially leads to revealing the web application's network ports in use, scanning the internal networks, and bypassing authorization.

Starting from release 4.4.3, Wallarm mitigates SSRF attack attempts. SSRF vulnerabilities are detected by all supported Wallarm versions.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• Apply the recommendations from the OWASP SSRF Prevention Cheat Sheet.

Cross-Site Request Forgery (CSRF)¶

Vulnerability

CWE code: CWE-352

Wallarm code: csrf

Description:

Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker’s choosing.

The corresponding vulnerability occurs due to the user's browser automatically adding user’s session cookies that are set for the target domain name while performing the cross-site request.

For most sites, these cookies include credentials associated with the site. Therefore, if the user is currently authenticated to the site, the site will have no way to distinguish between the forged request sent by the victim and a legitimate request sent by the victim.

As a result, the attacker can send a request to the vulnerable web application from a malicious website by posing as a legitimate user who is authenticated on the vulnerable site; the attacker does not even need to have access to that user's cookies.

Wallarm behavior:

Wallarm only discovers CSRF vulnerabilities, but does not detect and thus does not block CSRF attacks. CSRF problem is solved in all modern browsers via content security policies (CSP).

Remediation:

CSRF is solved by browsers, other protection methods are less useful but still can be used.

You may follow these recommendations:

• Employ anti-CSRF protection mechanisms, such as CSRF tokens and others.

• Set the SameSite cookie attribute.

• Apply the recommendations from the OWASP CSRF Prevention Cheat Sheet.

Forced browsing¶

Attack

CWE code: CWE-425

Wallarm code: dirbust

Description:

This attack belongs to the class of brute‑force attacks. The purpose of this attack is to detect a web application's hidden resources, namely directories and files. This is achieved by trying different file and directory names that are either generated based on some template or extracted from a prepared dictionary file.

A successful forced browsing attack potentially grants access to hidden resources that are not explicitly available from the web application interface but are exposed when accessed directly.

Remediation:

You may follow these recommendations:

• Restrict or limit users' access to those resources that they are not supposed to have direct access to (e.g., by employing some authentication or authorization mechanisms).

• Limit the number of requests per a certain time period for the web application.

• Limit the number of authentication/authorization attempts per a certain time period for the web application.

• Block new authentication/authorization attempts after a certain number of failed attempts.

• Set necessary and sufficient access rights for the web application's files and directories.

How to configure the Wallarm solution to protect applications from brute force →

Information exposure¶

Vulnerability/Attack

CWE codes: CWE-200 (see also: CWE-209, CWE-215, CWE-538, CWE-541, CWE-548)

Wallarm code: infoleak

Description:

The application either intentionally or unintentionally discloses sensitive information to a subject that is not authorized to access it.

The vulnerability of this type can be detected only by the method of passive detection. If the response to the request discloses sensitive information, Wallarm records an incident and an active vulnerability of the Information exposure type. Some kinds of sensitive information that can be detected by Wallarm include:

• System and environment status (for example: stack trace, warnings, fatal errors)

• Network status and configuration

• The application code or internal state

• Metadata (for example, logging of connections or message headers)

Remediation:

You may follow the recommendation to prohibit a web application from having the ability to display any sensitive information.

Vulnerable Component¶

Vulnerability

CWE codes: CWE-937, CWE-1035, CWE-1104

Wallarm code: vuln_component

Description:

This vulnerability occurs if your web application or API uses a vulnerable or outdated component. This can include an OS, web/application server, database management system (DBMS), runtime environments, libraries and other components.

This vulnerability is mapped with A06:2021 – Vulnerable and Outdated Components.

Remediation:

You may follow the recommendation to monitor and timely apply updates or configuration changes for the lifetime of the application or API, as follows:

• Remove unused dependencies, unnecessary features, components, files, and documentation.

• Continuously inventory the versions of both client-side and server-side components (e.g., frameworks, libraries) and their dependencies using tools like OWASP Dependency Check, retire.js, etc.

• Continuously monitor sources like Common Vulnerability and Exposures (CVE) and National Vulnerability Database (NVD) for vulnerabilities in the components.

• Only obtain components from official sources over secure links. Prefer signed packages to reduce the chance of including a modified, malicious component.

• Monitor for libraries and components that are unmaintained or do not create security patches for older versions. If patching is not possible, consider deploying a virtual patch to monitor, detect, or protect against the discovered issue.

Remote code execution (RCE)¶

Vulnerability/Attack

CWE codes: CWE-78, CWE-94 and others

Wallarm code: rce

Description:

An attacker can inject malicious code into a request to a web application, and the application will execute this code. Also, the attacker can try to execute certain commands for the operating system that the vulnerable web application runs on.

Provided that an RCE attack is successful, an attacker can perform a wide range of actions, including:

• Compromising the confidentiality, accessibility, and integrity of the vulnerable web application's data.

• Taking control of the operating system and the server that the web application runs on.

• Other possible actions.

This vulnerability occurs due to incorrect validation and parsing of user input.

Remediation:

You may follow the recommendation to sanitize and filter all user input to prevent an entity in the input from being executed.

Authentication bypass¶

Vulnerability

CWE code: CWE-288

Wallarm code: auth

Description:

Despite having authentication mechanisms in place, a web application can have alternative authentication methods that allow either bypassing the main authentication mechanism or exploiting its weaknesses. This combination of factors may result in an attacker gaining access with user or administrator permissions.

A successful authentication bypass attack potentially leads to disclosing users' confidential data or taking control of the vulnerable application with administrator permissions.

Remediation:

You may follow these recommendations:

• Improve and strengthen existing authentication mechanisms.

• Eliminate any alternative authentication methods that may allow attackers to access an application while bypassing the required authentication procedure via pre‑defined mechanisms.

• Apply the recommendations from the OWASP Authentication Cheat Sheet.

CRLF Injection¶

Vulnerability/Attack

CWE code: CWE-93

Wallarm code: crlf

Description:

CRLF injections represent a class of attacks that allow an attacker to inject the Carriage Return (CR) and Line Feed (LF) characters into a request to a server (e.g. HTTP request).

Combined with other factors, such CR/LF character injection can help to exploit a variety of vulnerabilities (e.g. HTTP Response Splitting CWE-113, HTTP Response Smuggling CWE-444).

A successful CRLF injection attack may give an attacker the ability to bypass firewalls, perform cache poisoning, replace legitimate web pages with malicious ones, perform the "Open redirect" attack, and plenty of other actions.

This vulnerability occurs due to the incorrect validation and parsing of user input.

Remediation:

You may follow the recommendation to sanitize and filter all user input to prevent an entity in the input from being executed.

LDAP Injection¶

Vulnerability/Attack

CWE code: CWE-90

Wallarm code: ldapi

Description:

LDAP injections represent a class of attacks that allow an attacker to alter LDAP search filters by modifying requests to an LDAP server.

A successful LDAP injection attack potentially grants access to the read and write operations on confidential data about LDAP users and hosts.

This vulnerability occurs due to the incorrect validation and parsing of user input.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• Apply the recommendations from the OWASP LDAP Injection Prevention Cheat Sheet.

NoSQL Injection¶

Vulnerability/Attack

CWE code: CWE-943

Wallarm code: nosqli

Description:

Vulnerability to this attack occurs due to insufficient filtering of user input. A NoSQL injection attack is performed by injecting a specially crafted query to a NoSQL database.

Remediation:

You may follow the recommendation to sanitize and filter all user input to prevent an entity in the input from being executed.

Path Traversal¶

Vulnerability/Attack

CWE code: CWE-22

Wallarm code: ptrav

Description:

A path traversal attack allows an attacker to access files and directories with confidential data stored in the file system where the vulnerable web application resides by altering existing paths via the web application's parameters.

Vulnerability to this attack occurs due to insufficient filtering of user input when a user requests a file or directory via the web application.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• Additional recommendations for mitigating such attacks are available here.

SQL Injection¶

Vulnerability/Attack

CWE code: CWE-89

Wallarm code: sqli

Description:

Vulnerability to this attack occurs due to insufficient filtration of user input. An SQL injection attack is performed by injecting a specially crafted query to an SQL database.

An SQL injection attack allows an attacker to inject arbitrary SQL code into an SQL query. This potentially leads to the attacker being granted access to read and modify confidential data as well as to DBMS administrator rights.

Remediation:

You may follow these recommendations:

• Sanitize and filter all parameters that a web application receives as input to prevent an entity in the input from being executed.

• Apply the recommendations from the OWASP SQL Injection Prevention Cheat Sheet.

Email Injection¶

Attack

CWE code: CWE-20, CWE-150, CWE-88

Wallarm code: mail_injection

Description:

Email Injection is a malicious IMAP/SMTP expression usually sent via the web application contact form to change standard email server behavior.

Vulnerability to this attack occurs due to poor validation of the data inputted in the contact form. Email Injection allows bypassing email client restrictions, stealing user data and sending spam.

Remediation:

• Sanitize and filter all user input to prevent malicious payloads in the input from being executed.

• Apply the recommendations from the OWASP Input Validation Cheatsheet.

SSI Injection¶

Attack

CWE code: CWE-96, CWE-97

Wallarm code: ssi

Description:

SSI (Server Side Includes) is a simple interpreted server-side scripting language most useful for including the contents of one or more files into a web page on a web server. It is supported by the web servers Apache and NGINX.

SSI Injection allows the exploitation of a web application by injecting malicious payloads in HTML pages or executing arbitrary codes remotely. It can be exploited through manipulation of SSI in use in the application or force its use through user input fields.

Example:

An attacker can change the message output and change the user behavior. SSI Injection example:

<!--#config errmsg="Access denied, please enter your username and password"-->

Remediation:

• Sanitize and filter all user input to prevent malicious payloads in the input from being executed.

• Apply the recommendations from the OWASP Input Validation Cheatsheet.

Mass Assignment¶

Attack

Wallarm code: mass_assignment

Description:

During a Mass Assignment attack, attackers try to bind HTTP request parameters into program code variables or objects. If an API is vulnerable and allows binding, attackers may change sensitive object properties that are not intended to be exposed, which could lead to privilege escalation, bypassing security mechanisms, and more.

APIs vulnerable to Mass Assignment attacks allow converting client input to internal variables or object properties without proper filtering. This vulnerability is included in the OWASP API Top 10 (API6:2019 Mass Assignment) list of most serious API security risks.

Starting from release 4.4.3, Wallarm mitigates Mass Assignment attempts.

Remediation:

To protect the API, you may follow these recommendations:

• Avoid using functions that automatically bind a client’s input into code variables or object properties.

• Use built-in function features to whitelist only the properties that should be updated by the client and blacklist private properties.

• If applicable, explicitly define and enforce schemas for the input data payloads.

Weak JWT¶

Vulnerability

CWE code: CWE-1270, CWE-1294

Wallarm code: weak_auth

Description:

JSON Web Token (JWT) is a popular authentication standard used to exchange data between resources like APIs securely.

JWT compromisation is a common aim of attackers as breaking authentication mechanisms provides them full access to web applications and APIs. The weaker JWTs, the higher chance for it to be compromised.

Wallarm behavior:

Wallarm detects weak JWTs only if the filtering node has version 4.4 or above and there is the Weak JWT trigger enabled.

Wallarm considers JWTs to be weak if they are:

• Unencrypted - there is no signing algorithm (the alg field is none or absent).

• Signed using compromised secret keys.

Once a weak JWT is detected, Wallarm records the corresponding vulnerability.

Remediation:

• Apply the recommendations from the OWASP JSON Web Token Cheat Sheet

• Check if your JWT implementation is vulnerable for well-known secrets

API abuse¶

Attack

Wallarm code: api_abuse

Description:

A set of basic bot types that includes server response time increase, fake account creation, and scalping.

Wallarm behavior:

Wallarm detects API abuse only if the filtering node has version 4.2 or above.

The API Abuse Prevention module uses the complex bot detection model to detect the following bot types:

• API abuse targeted at server response time increase or server unavailability. Usually, it is achieved by malicious traffic spikes.

• Fake account creation and Spamming are creation of fake accounts or confirmation of fake content (e.g. feedback). Usually, it does not result in service unavailability but slows down or degrades regular business processes, e.g.:

  • Processing of real user requests by the support team
  • Collecting real user statistics by the marketing team

• Scalping is characterized by bots making online store products unavailable for real customers, e.g. by reserving all items so that they become out of stock but do not make any profit.

If the metrics point to bot attack signs, the module denylists or graylists the source of the anomaly traffic for 1 hour.

Remediation:

You may follow these recommendations:

• Get familiar with the OWASP description for automated threats to web applications.

• Denylist IP addresses of regions and sources (like Tor), definitely not related to your application.

• Configure server-side rate limit for requests.

• Use additional CAPTCHA solutions.

• Search your application analytics for the bot attack signs.

API abuse - Account takeover¶

Attack

Wallarm code: api_abuse

Description:

A type of cyber attack where a malicious actor gains access to someone else's account without their permission or knowledge. This can happen when an attacker obtains a user's login credentials through various means such as phishing, malware, or social engineering. Once they have access to the account, they can use it for various purposes, such as stealing sensitive information, conducting fraudulent transactions, or spreading spam or malware. Account takeover attacks can have serious consequences for individuals and businesses, including financial losses, reputational damage, and loss of trust.

Wallarm behavior:

Wallarm detects API abuse only if the filtering node has version 4.2 or above.

The API Abuse Prevention module uses the complex bot detection model to detect the following account takeover bot types:

• Credential cracking includes brute force, dictionary (word list) and guessing attacks used against authentication processes of the application to identify valid account credentials.

• Credential stuffing is the automated injection of stolen user credentials into website login forms, in order to fraudulently gain access to user accounts.

Remediation:

You may follow these recommendations:

• Get familiar with the OWASP description for automated threats to web applications.

• Use strong passwords.

• Do not use the same passwords for different resources.

• Enable two-factor authentication.

• Use additional CAPTCHA solutions.

• Monitor accounts for suspicious activities.

API abuse - Security crawlers¶

Attack

Wallarm code: api_abuse

Description:

While security crawlers are designed to scan websites and detect vulnerabilities and security issues, they can also be used for malicious purposes. Malicious actors may use them to identify vulnerable websites and exploit them for their own gain.

Furthermore, some security crawlers may be poorly designed and inadvertently cause harm to websites by overwhelming servers, causing crashes, or creating other types of disruptions.

Wallarm behavior:

Wallarm detects API abuse only if the filtering node has version 4.2 or above.

The API Abuse Prevention module uses the complex bot detection model to detect the following security crawlers bot types:

• Fingerprinting exploits specific requests which are sent to the application eliciting information in order to profile the application.

• Footprinting is an information gathering with the objective of learning as much as possible about the composition, configuration and security mechanisms of the application.

• Vulnerability scanning is characterized by service vulnerability search.

Remediation:

You may follow these recommendations:

• Get familiar with the OWASP description for automated threats to web applications.

• Use SSL certificates.

• Use additional CAPTCHA solutions.

• Implement rate limiting.

• Monitor your traffic to look for patterns that may indicate malicious activity.

• Use robots.txt file to tell search engine crawlers which pages they can and cannot crawl.

• Regularly update software.

• Use a content delivery network (CDN).

API abuse - Scraping¶

Attack

Wallarm code: api_abuse

Description:

Web scraping, also known as data scraping or web harvesting, is the process of automatically extracting data from websites. It involves using software or code to retrieve and extract data from web pages and save it in a structured format such as a spreadsheet or database.

Web scraping can be used for malicious purposes. For example, scrapers can be used to steal sensitive information such as login credentials, personal information, or financial data from websites. Scrapers can also be used to spam or scrape data from a website in a way that degrades its performance, causing denial of service (DoS) attacks.

Wallarm behavior:

Wallarm detects API abuse only if the filtering node has version 4.2 or above.

The API Abuse Prevention module uses the complex bot detection model to detect the scraping bot type which is collecting accessible data and/or processed output from the application that may result in private or non-free content becoming available for any user.

Remediation:

You may follow these recommendations:

• Get familiar with the OWASP description for automated threats to web applications.

• Use additional CAPTCHA solutions.

• Use robots.txt file to tell search engine crawlers which pages they can and cannot crawl.

• Monitor your traffic to look for patterns that may indicate malicious activity.

• Implement rate limiting.

• Obfuscate or encrypt data.

• Take legal action.

The list of special attacks and vulnerabilities¶

Virtual patch¶

Attack

Wallarm code: vpatch

Description:

A request is marked as a vpatch if it is part of an attack that was mitigated by the virtual patch mechanism.

Unsafe XML header¶

Attack

Wallarm code: invalid_xml

Description:

A request is marked as an invalid_xml if its body contains an XML document and the document encoding differs from the encoding stated in the XML header.

Overlimiting of computational resources¶

Attack

Wallarm code: overlimit_res

Description:

There are two scenarios the Wallarm node marks a request as the overlimit_res attack:

• The Wallarm node is configured in such a way that it should spend no more than N milliseconds on incoming requests processing (default value: 1000). If the request is not processed during the specified timeframe, then the processing of the request will be stopped and the request marked as an overlimit_res attack.

  You can specify the custom time limit and change the default node behavior when the limit is exceeded using the rule Fine-tune the overlimit_res attack detection.

  Limiting the request processing time prevents the bypass attacks aimed at the Wallarm nodes. In some cases, the requests marked as overlimit_res can indicate insufficient resources allocated for the Wallarm node modules that lead to long request processing time.

• The request uploads the gzip file weighing more than 512 MB.

DDoS (Distributed Denial of Service) attack¶

A DDoS (Distributed Denial of Service) attack is a type of cyber attack in which an attacker seeks to make a website or online service unavailable by overwhelming it with traffic from multiple sources.

There are many techniques that attackers can use to launch a DDoS attack, and the methods and tools they use can significantly vary. Some attacks are relatively simple and use low-level techniques such as sending large numbers of connection requests to a server, while others are more sophisticated and use complex tactics such as spoofing IP addresses or exploiting vulnerabilities in network infrastructure.

Read our guide on protecting resources against DDoS