Upraviť

Zdieľať cez

Web Application Firewall DRS and CRS rule groups and rules

  • Článok

The Azure-managed rule sets in the Application Gateway web application firewall (WAF) actively protect web applications from common vulnerabilities and exploits. These rule sets, managed by Azure, receive updates as necessary to guard against new attack signatures. The default rule set also incorporates the Microsoft Threat Intelligence Collection rules. The Microsoft Intelligence team collaborates in writing these rules, ensuring enhanced coverage, specific vulnerability patches, and improved false positive reduction.

You also have the option of using rules that are defined based on the OWASP core rule sets 3.2, 3.1, 3.0, or 2.2.9.

You can disable rules individually, or set specific actions for each rule. This article lists the current rules and rule sets available. If a published rule set requires an update, we'll document it here.

Note

When a ruleset version is changed in a WAF Policy, any existing customizations you made to your ruleset will be reset to the defaults for the new ruleset. See: Upgrading or changing ruleset version.

Default rule sets

The Azure-managed Default Rule Set (DRS) includes rules against the following threat categories:

  • Cross-site scripting
  • Java attacks
  • Local file inclusion
  • PHP injection attacks
  • Remote command execution
  • Remote file inclusion
  • Session fixation
  • SQL injection protection
  • Protocol attackers The version number of the DRS increments when new attack signatures are added to the rule set.

Microsoft Threat Intelligence Collection rules

The Microsoft Threat Intelligence Collection rules are written in partnership with the Microsoft Threat Intelligence team to provide increased coverage, patches for specific vulnerabilities, and better false positive reduction.

Note

Please use the following guidance to tune WAF while you get started with 2.1 on Application Gateway WAF. Details of the rules are described next.

Rule ID Rule Group Description Details
942110 SQLI SQL Injection Attack: Common Injection Testing Detected Disable, Replaced by MSTIC rule 99031001
942150 SQLI SQL Injection Attack Disable, Replaced by MSTIC rule 99031003
942260 SQLI Detects basic SQL authentication bypass attempts 2/3 Disable, Replaced by MSTIC rule 99031004
942430 SQLI Restricted SQL Character Anomaly Detection (args): # of special characters exceeded (12) Disable, Too many false positives.
942440 SQLI SQL Comment Sequence Detected Disable, Replaced by MSTIC rule 99031002
99005006 MS-ThreatIntel-WebShells Spring4Shell Interaction Attempt Keep the rule enabled to prevent against SpringShell vulnerability
99001014 MS-ThreatIntel-CVEs Attempted Spring Cloud routing-expression injection CVE-2022-22963 Keep the rule enabled to prevent against SpringShell vulnerability
99001015 MS-ThreatIntel-WebShells Attempted Spring Framework unsafe class object exploitation CVE-2022-22965 Keep the rule enabled to prevent against SpringShell vulnerability
99001016 MS-ThreatIntel-WebShells Attempted Spring Cloud Gateway Actuator injection CVE-2022-22947 Keep the rule enabled to prevent against SpringShell vulnerability
99001017 MS-ThreatIntel-CVEs Attempted Apache Struts file upload exploitation CVE-2023-50164 Set action to Block to prevent against Apache Struts vulnerability. Anomaly Score not supported for this rule.

Core rule sets

The Application Gateway WAF comes preconfigured with CRS 3.2 by default, but you can choose to use any other supported CRS version.

CRS 3.2 offers a new engine and new rule sets defending against Java injections, an initial set of file upload checks, and fewer false positives compared with earlier versions of CRS. You can also customize rules to suit your needs. Learn more about the new Azure WAF engine.

Manages rules

The WAF protects against the following web vulnerabilities:

  • SQL-injection attacks
  • Cross-site scripting attacks
  • Other common attacks, such as command injection, HTTP request smuggling, HTTP response splitting, and remote file inclusion
  • HTTP protocol violations
  • HTTP protocol anomalies, such as missing host user-agent and accept headers
  • Bots, crawlers, and scanners
  • Common application misconfigurations (for example, Apache and IIS)

Tuning of Managed rule sets

Both DRS and CRS are enabled by default in Detection mode in your WAF policies. You can disable or enable individual rules within the Managed Rule Set to meet your application requirements. You can also set specific actions per rule. The DRS/CRS supports block, log and anomaly score actions. The Bot Manager ruleset supports the allow, block and log actions.

Sometimes you might need to omit certain request attributes from a WAF evaluation. A common example is Active Directory-inserted tokens that are used for authentication. You can configure exclusions to apply when specific WAF rules are evaluated, or to apply globally to the evaluation of all WAF rules. Exclusion rules apply to your whole web application. For more information, see Web Application Firewall (WAF) with Application Gateway exclusion lists.

By default, DRS version 2.1 / CRS version 3.2 and above uses anomaly scoring when a request matches a rule. CRS 3.1 and below blocks matching requests by default. Additionally, custom rules can be configured in the same WAF policy if you want to bypass any of the preconfigured rules in the Core Rule Set.

Custom rules are always applied before rules in the Core Rule Set are evaluated. If a request matches a custom rule, the corresponding rule action is applied. The request is either blocked or passed through to the back-end. No other custom rules or the rules in the Core Rule Set are processed.

Anomaly scoring

When you use CRS or DRS 2.1 and later, your WAF is configured to use anomaly scoring by default. Traffic that matches any rule isn't immediately blocked, even when your WAF is in prevention mode. Instead, the OWASP rule sets define a severity for each rule: Critical, Error, Warning, or Notice. The severity affects a numeric value for the request, which is called the anomaly score:

Rule severity Value contributed to anomaly score
Critical 5
Error 4
Warning 3
Notice 2

If the anomaly score is 5 or greater, and the WAF is in Prevention mode, the request is blocked. If the anomaly score is 5 or greater, and the WAF is in Detection mode, the request is logged but not blocked.

For example, a single Critical rule match is enough for the WAF to block a request when in Prevention mode, because the overall anomaly score is 5. However, one Warning rule match only increases the anomaly score by 3, which isn't enough by itself to block the traffic. When an anomaly rule is triggered, it shows a "Matched" action in the logs. If the anomaly score is 5 or greater, there is a separate rule triggered with either "Blocked" or "Detected" action depending on whether WAF policy is in Prevention or Detection mode. For more information, please see Anomaly Scoring mode.

Upgrading or changing ruleset version

If you are upgrading, or assigning a new ruleset version, and would like to preserve existing rule overrides and exclusions, it is recommended to use PowerShell, CLI, REST API, or a templates to make ruleset version changes. A new version of a ruleset can have newer rules, additional rule groups, and may have updates to existing signatures to enforce better security and reduce false positives. It is recommended to validate changes in a test environment, fine tune if necessary, and then deploy in a production environment.

Note

If you are using the Azure portal to assign a new managed ruleset to a WAF policy, all the previous customizations from the existing managed ruleset such as rule state, rule actions, and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules, policy settings, and global exclusions will remain unaffected during the new ruleset assignment. You will need to redefine rule overrides and validate changes before deploying in a production environment.

DRS 2.1

DRS 2.1 rules offer better protection than earlier versions of the DRS. It includes more rules developed by the Microsoft Threat Intelligence team and updates to signatures to reduce false positives. It also supports transformations beyond just URL decoding.

DRS 2.1 includes 17 rule groups, as shown in the following table. Each group contains multiple rules, and you can customize behavior for individual rules, rule groups, or entire rule set. DRS 2.1 is baselined off the Open Web Application Security Project (OWASP) Core Rule Set (CRS) 3.3.2 and includes additional proprietary protections rules developed by Microsoft Threat Intelligence team.

Rule group ruleGroupName Description
General General General group
METHOD-ENFORCEMENT METHOD-ENFORCEMENT Lock-down methods (PUT, PATCH)
PROTOCOL-ENFORCEMENT PROTOCOL-ENFORCEMENT Protect against protocol and encoding issues
PROTOCOL-ATTACK PROTOCOL-ATTACK Protect against header injection, request smuggling, and response splitting
APPLICATION-ATTACK-LFI LFI Protect against file and path attacks
APPLICATION-ATTACK-RFI RFI Protect against remote file inclusion (RFI) attacks
APPLICATION-ATTACK-RCE RCE Protect again remote code execution attacks
APPLICATION-ATTACK-PHP PHP Protect against PHP-injection attacks
APPLICATION-ATTACK-NodeJS NODEJS Protect against Node JS attacks
APPLICATION-ATTACK-XSS XSS Protect against cross-site scripting attacks
APPLICATION-ATTACK-SQLI SQLI Protect against SQL-injection attacks
APPLICATION-ATTACK-SESSION-FIXATION FIX Protect against session-fixation attacks
APPLICATION-ATTACK-SESSION-JAVA JAVA Protect against JAVA attacks
MS-ThreatIntel-WebShells MS-ThreatIntel-WebShells Protect against Web shell attacks
MS-ThreatIntel-AppSec MS-ThreatIntel-AppSec Protect against AppSec attacks
MS-ThreatIntel-SQLI MS-ThreatIntel-SQLI Protect against SQLI attacks
MS-ThreatIntel-CVEs MS-ThreatIntel-CVEs Protect against CVE attacks

OWASP CRS 3.2

CRS 3.2 includes 14 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled. The ruleset is based off OWASP CRS 3.2.0 version.

Note

CRS 3.2 is only available on the WAF_v2 SKU. Because CRS 3.2 runs on the new Azure WAF engine, you can't downgrade to CRS 3.1 or earlier. If you need to downgrade, contact Azure Support.

Rule group name Description
General General group
KNOWN-CVES Help detect new and known CVEs
REQUEST-911-METHOD-ENFORCEMENT Lock-down methods (PUT, PATCH)
REQUEST-913-SCANNER-DETECTION Protect against port and environment scanners
REQUEST-920-PROTOCOL-ENFORCEMENT Protect against protocol and encoding issues
REQUEST-921-PROTOCOL-ATTACK Protect against header injection, request smuggling, and response splitting
REQUEST-930-APPLICATION-ATTACK-LFI Protect against file and path attacks
REQUEST-931-APPLICATION-ATTACK-RFI Protect against remote file inclusion (RFI) attacks
REQUEST-932-APPLICATION-ATTACK-RCE Protect again remote code execution attacks
REQUEST-933-APPLICATION-ATTACK-PHP Protect against PHP-injection attacks
REQUEST-941-APPLICATION-ATTACK-XSS Protect against cross-site scripting attacks
REQUEST-942-APPLICATION-ATTACK-SQLI Protect against SQL-injection attacks
REQUEST-943-APPLICATION-ATTACK-SESSION-FIXATION Protect against session-fixation attacks
REQUEST-944-APPLICATION-ATTACK-JAVA Protect against JAVA attacks

OWASP CRS 3.1

CRS 3.1 includes 14 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled. The ruleset is based off OWASP CRS 3.1.1 version.

Note

CRS 3.1 is only available on the WAF_v2 SKU.

Rule group name Description
General General group
KNOWN-CVES Help detect new and known CVEs
REQUEST-911-METHOD-ENFORCEMENT Lock-down methods (PUT, PATCH)
REQUEST-913-SCANNER-DETECTION Protect against port and environment scanners
REQUEST-920-PROTOCOL-ENFORCEMENT Protect against protocol and encoding issues
REQUEST-921-PROTOCOL-ATTACK Protect against header injection, request smuggling, and response splitting
REQUEST-930-APPLICATION-ATTACK-LFI Protect against file and path attacks
REQUEST-931-APPLICATION-ATTACK-RFI Protect against remote file inclusion (RFI) attacks
REQUEST-932-APPLICATION-ATTACK-RCE Protect again remote code execution attacks
REQUEST-933-APPLICATION-ATTACK-PHP Protect against PHP-injection attacks
REQUEST-941-APPLICATION-ATTACK-XSS Protect against cross-site scripting attacks
REQUEST-942-APPLICATION-ATTACK-SQLI Protect against SQL-injection attacks
REQUEST-943-APPLICATION-ATTACK-SESSION-FIXATION Protect against session-fixation attacks
REQUEST-944-APPLICATION-ATTACK-SESSION-JAVA Protect against JAVA attacks

OWASP CRS 3.0

CRS 3.0 includes 13 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled. The ruleset is based off OWASP CRS 3.0.0 version.

Rule group name Description
General General group
KNOWN-CVES Help detect new and known CVEs
REQUEST-911-METHOD-ENFORCEMENT Lock-down methods (PUT, PATCH)
REQUEST-913-SCANNER-DETECTION Protect against port and environment scanners
REQUEST-920-PROTOCOL-ENFORCEMENT Protect against protocol and encoding issues
REQUEST-921-PROTOCOL-ATTACK Protect against header injection, request smuggling, and response splitting
REQUEST-930-APPLICATION-ATTACK-LFI Protect against file and path attacks
REQUEST-931-APPLICATION-ATTACK-RFI Protect against remote file inclusion (RFI) attacks
REQUEST-932-APPLICATION-ATTACK-RCE Protect again remote code execution attacks
REQUEST-933-APPLICATION-ATTACK-PHP Protect against PHP-injection attacks
REQUEST-941-APPLICATION-ATTACK-XSS Protect against cross-site scripting attacks
REQUEST-942-APPLICATION-ATTACK-SQLI Protect against SQL-injection attacks
REQUEST-943-APPLICATION-ATTACK-SESSION-FIXATION Protect against session-fixation attacks

OWASP CRS 2.2.9

CRS 2.2.9 includes 10 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled.

Note

CRS 2.2.9 is no longer supported for new WAF policies. We recommend you upgrade to the latest CRS 3.2/DRS 2.1 and greater versions.

Rule group name Description
crs_20_protocol_violations Protect against protocol violations (such as invalid characters or a GET with a request body)
crs_21_protocol_anomalies Protect against incorrect header information
crs_23_request_limits Protect against arguments or files that exceed limitations
crs_30_http_policy Protect against restricted methods, headers, and file types
crs_35_bad_robots Protect against web crawlers and scanners
crs_40_generic_attacks Protect against generic attacks (such as session fixation, remote file inclusion, and PHP injection)
crs_41_sql_injection_attacks Protect against SQL-injection attacks
crs_41_xss_attacks Protect against cross-site scripting attacks
crs_42_tight_security Protect against path-traversal attacks
crs_45_trojans Protect against backdoor trojans

Bot Manager 1.0

The Bot Manager 1.0 rule set provides protection against malicious bots and detection of good bots. The rules provide granular control over bots detected by WAF by categorizing bot traffic as Good, Bad, or Unknown bots.

Rule group Description
BadBots Protect against bad bots
GoodBots Identify good bots
UnknownBots Identify unknown bots

Bot Manager 1.1

The Bot Manager 1.1 rule set is an enhancement to Bot Manager 1.0 rule set. It provides enhanced protection against malicious bots, and increases good bot detection.

Rule group Description
BadBots Protect against bad bots
GoodBots Identify good bots
UnknownBots Identify unknown bots

The following rule groups and rules are available when using Web Application Firewall on Application Gateway.

2.1 rule sets

General

RuleId Description
200002 Failed to parse request body.
200003 Multipart request body failed strict validation

METHOD ENFORCEMENT

RuleId Description
911100 Method isn't allowed by policy

PROTOCOL-ENFORCEMENT

RuleId Description
920100 Invalid HTTP Request Line
920120 Attempted multipart/form-data bypass
920121 Attempted multipart/form-data bypass
920160 Content-Length HTTP header isn't numeric.
920170 GET or HEAD Request with Body Content.
920171 GET or HEAD Request with Transfer-Encoding.
920180 POST request missing Content-Length Header.
920181 Content-Length and Transfer-Encoding headers present 99001003
920190 Range: Invalid Last Byte Value.
920200 Range: Too many fields (6 or more)
920201 Range: Too many fields for pdf request (35 or more)
920210 Multiple/Conflicting Connection Header Data Found.
920220 URL Encoding Abuse Attack Attempt
920230 Multiple URL Encoding Detected
920240 URL Encoding Abuse Attack Attempt
920260 Unicode Full/Half Width Abuse Attack Attempt
920270 Invalid character in request (null character)
920271 Invalid character in request (non printable characters)
920280 Request Missing a Host Header
920290 Empty Host Header
920300 Request Missing an Accept Header
920310 Request Has an Empty Accept Header
920311 Request Has an Empty Accept Header
920320 Missing User Agent Header
920330 Empty User Agent Header
920340 Request Containing Content, but Missing Content-Type header
920341 Request containing content requires Content-Type header
920350 Host header is a numeric IP address
920420 Request content type isn't allowed by policy
920430 HTTP protocol version isn't allowed by policy
920440 URL file extension is restricted by policy
920450 HTTP header is restricted by policy
920470 Illegal Content-Type header
920480 Request content type charset isn't allowed by policy
920500 Attempt to access a backup or working file

PROTOCOL-ATTACK

RuleId Description
921110 HTTP Request Smuggling Attack
921120 HTTP Response Splitting Attack
921130 HTTP Response Splitting Attack
921140 HTTP Header Injection Attack via headers
921150 HTTP Header Injection Attack via payload (CR/LF detected)
921151 HTTP Header Injection Attack via payload (CR/LF detected)
921160 HTTP Header Injection Attack via payload (CR/LF and header-name detected)
921190 HTTP Splitting (CR/LF in request filename detected)
921200 LDAP Injection Attack

LFI - Local File Inclusion

RuleId Description
930100 Path Traversal Attack (/../)
930110 Path Traversal Attack (/../)
930120 OS File Access Attempt
930130 Restricted File Access Attempt

RFI - Remote File Inclusion

RuleId Description
931100 Possible Remote File Inclusion (RFI) Attack: URL Parameter using IP Address
931110 Possible Remote File Inclusion (RFI) Attack: Common RFI Vulnerable Parameter Name used w/URL Payload
931120 Possible Remote File Inclusion (RFI) Attack: URL Payload Used w/Trailing Question Mark Character (?)
931130 Possible Remote File Inclusion (RFI) Attack: Off-Domain Reference/Link

RCE - Remote Command Execution

RuleId Description
932100 Remote Command Execution: Unix Command Injection
932105 Remote Command Execution: Unix Command Injection
932110 Remote Command Execution: Windows Command Injection
932115 Remote Command Execution: Windows Command Injection
932120 Remote Command Execution: Windows PowerShell Command Found
932130 Remote Command Execution: Unix Shell Expression or Confluence Vulnerability (CVE-2022-26134) Found
932140 Remote Command Execution: Windows FOR/IF Command Found
932150 Remote Command Execution: Direct Unix Command Execution
932160 Remote Command Execution: Unix Shell Code Found
932170 Remote Command Execution: Shellshock (CVE-2014-6271)
932171 Remote Command Execution: Shellshock (CVE-2014-6271)
932180 Restricted File Upload Attempt

PHP Attacks

RuleId Description
933100 PHP Injection Attack: Opening/Closing Tag Found
933110 PHP Injection Attack: PHP Script File Upload Found
933120 PHP Injection Attack: Configuration Directive Found
933130 PHP Injection Attack: Variables Found
933140 PHP Injection Attack: I/O Stream Found
933150 PHP Injection Attack: High-Risk PHP Function Name Found
933151 PHP Injection Attack: Medium-Risk PHP Function Name Found
933160 PHP Injection Attack: High-Risk PHP Function Call Found
933170 PHP Injection Attack: Serialized Object Injection
933180 PHP Injection Attack: Variable Function Call Found
933200 PHP Injection Attack: Wrapper scheme detected
933210 PHP Injection Attack: Variable Function Call Found

Node JS Attacks

RuleId Description
934100 Node.js Injection Attack

XSS - Cross-site Scripting

RuleId Description
941100 XSS Attack Detected via libinjection
941101 XSS Attack Detected via libinjection.
This rule detects requests with a Referer header.
941110 XSS Filter - Category 1: Script Tag Vector
941120 XSS Filter - Category 2: Event Handler Vector
941130 XSS Filter - Category 3: Attribute Vector
941140 XSS Filter - Category 4: JavaScript URI Vector
941150 XSS Filter - Category 5: Disallowed HTML Attributes
941160 NoScript XSS InjectionChecker: HTML Injection
941170 NoScript XSS InjectionChecker: Attribute Injection
941180 Node-Validator Blocklist Keywords
941190 XSS Using style sheets
941200 XSS using VML frames
941210 XSS using obfuscated JavaScript
941220 XSS using obfuscated VB Script
941230 XSS using 'embed' tag
941240 XSS using 'import' or 'implementation' attribute
941250 IE XSS Filters - Attack Detected.
941260 XSS using 'meta' tag
941270 XSS using 'link' href
941280 XSS using 'base' tag
941290 XSS using 'applet' tag
941300 XSS using 'object' tag
941310 US-ASCII Malformed Encoding XSS Filter - Attack Detected.
941320 Possible XSS Attack Detected - HTML Tag Handler
941330 IE XSS Filters - Attack Detected.
941340 IE XSS Filters - Attack Detected.
941350 UTF-7 Encoding IE XSS - Attack Detected.
941360 JavaScript obfuscation detected.
941370 JavaScript global variable found
941380 AngularJS client side template injection detected

SQLI - SQL Injection

RuleId Description
942100 SQL Injection Attack Detected via libinjection
942110 SQL Injection Attack: Common Injection Testing Detected
942120 SQL Injection Attack: SQL Operator Detected
942130 SQL Injection Attack: SQL Tautology Detected.
942140 SQL Injection Attack: Common DB Names Detected
942150 SQL Injection Attack
942160 Detects blind sqli tests using sleep() or benchmark().
942170 Detects SQL benchmark and sleep injection attempts including conditional queries
942180 Detects basic SQL authentication bypass attempts 1/3
942190 Detects MSSQL code execution and information gathering attempts
942200 Detects MySQL comment-/space-obfuscated injections and backtick termination
942210 Detects chained SQL injection attempts 1/2
942220 Looking for integer overflow attacks, these are taken from skipfish, except 3.0.00738585072007e-308 is the "magic number" crash
942230 Detects conditional SQL injection attempts
942240 Detects MySQL charset switch and MSSQL DoS attempts
942250 Detects MATCH AGAINST, MERGE and EXECUTE IMMEDIATE injections
942260 Detects basic SQL authentication bypass attempts 2/3
942270 Looking for basic sql injection. Common attack string for mysql, oracle, and others.
942280 Detects Postgres pg_sleep injection, waitfor delay attacks and database shutdown attempts
942290 Finds basic MongoDB SQL injection attempts
942300 Detects MySQL comments, conditions, and ch(a)r injections
942310 Detects chained SQL injection attempts 2/2
942320 Detects MySQL and PostgreSQL stored procedure/function injections
942330 Detects classic SQL injection probings 1/2
942340 Detects basic SQL authentication bypass attempts 3/3
942350 Detects MySQL UDF injection and other data/structure manipulation attempts
942360 Detects concatenated basic SQL injection and SQLLFI attempts
942361 Detects basic SQL injection based on keyword alter or union
942370 Detects classic SQL injection probings 2/2
942380 SQL Injection Attack
942390 SQL Injection Attack
942400 SQL Injection Attack
942410 SQL Injection Attack
942430 Restricted SQL Character Anomaly Detection (args): # of special characters exceeded (12)
942440 SQL Comment Sequence Detected
942450 SQL Hex Encoding Identified
942460 Meta-Character Anomaly Detection Alert - Repetitive Non-Word Characters
942470 SQL Injection Attack
942480 SQL Injection Attack
942500 MySQL in-line comment detected.
942510 SQLi bypass attempt by ticks or backticks detected.

SESSION-FIXATION

RuleId Description
943100 Possible Session Fixation Attack: Setting Cookie Values in HTML
943110 Possible Session Fixation Attack: SessionID Parameter Name with Off-Domain Referrer
943120 Possible Session Fixation Attack: SessionID Parameter Name with No Referrer

JAVA Attacks

RuleId Description
944100 Remote Command Execution: Apache Struts, Oracle WebLogic
944110 Detects potential payload execution
944120 Possible payload execution and remote command execution
944130 Suspicious Java classes
944200 Exploitation of Java deserialization Apache Commons
944210 Possible use of Java serialization
944240 Remote Command Execution: Java serialization and Log4j vulnerability (CVE-2021-44228, CVE-2021-45046)
944250 Remote Command Execution: Suspicious Java method detected

MS-ThreatIntel-WebShells

RuleId Description
99005002 Web Shell Interaction Attempt (POST)
99005003 Web Shell Upload Attempt (POST) - CHOPPER PHP
99005004 Web Shell Upload Attempt (POST) - CHOPPER ASPX
99005005 Web Shell Interaction Attempt
99005006 Spring4Shell Interaction Attempt

MS-ThreatIntel-AppSec

RuleId Description
99030001 Path Traversal Evasion in Headers (/.././../)
99030002 Path Traversal Evasion in Request Body (/.././../)

MS-ThreatIntel-SQLI

RuleId Description
99031001 SQL Injection Attack: Common Injection Testing Detected
99031002 SQL Comment Sequence Detected.
99031003 SQL Injection Attack
99031004 Detects basic SQL authentication bypass attempts 2/3

MS-ThreatIntel-CVEs

RuleId Description
99001001 Attempted F5 tmui (CVE-2020-5902) REST API Exploitation with known credentials
99001002 Attempted Citrix NSC_USER directory traversal CVE-2019-19781
99001003 Attempted Atlassian Confluence Widget Connector exploitation CVE-2019-3396
99001004 Attempted Pulse Secure custom template exploitation CVE-2020-8243
99001005 Attempted SharePoint type converter exploitation CVE-2020-0932
99001006 Attempted Pulse Connect directory traversal CVE-2019-11510
99001007 Attempted Junos OS J-Web local file inclusion CVE-2020-1631
99001008 Attempted Fortinet path traversal CVE-2018-13379
99001009 Attempted Apache struts ognl injection CVE-2017-5638
99001010 Attempted Apache struts ognl injection CVE-2017-12611
99001011 Attempted Oracle WebLogic path traversal CVE-2020-14882
99001012 Attempted Telerik WebUI insecure deserialization exploitation CVE-2019-18935
99001013 Attempted SharePoint insecure XML deserialization CVE-2019-0604
99001014 Attempted Spring Cloud routing-expression injection CVE-2022-22963
99001015 Attempted Spring Framework unsafe class object exploitation CVE-2022-22965
99001016 Attempted Spring Cloud Gateway Actuator injection CVE-2022-22947
99001017* Attempted Apache Struts file upload exploitation CVE-2023-50164

*This rule's action is set to log by default. Set action to Block to prevent against Apache Struts vulnerability. Anomaly Score not supported for this rule.

Note

When reviewing your WAF's logs, you might see rule ID 949110. The description of the rule might include Inbound Anomaly Score Exceeded.

This rule indicates that the total anomaly score for the request exceeded the maximum allowable score. For more information, see Anomaly scoring.

Next steps