aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Buechler <cmb@pfsense.org>2015-12-01 19:09:30 -0600
committerChris Buechler <cmb@pfsense.org>2015-12-01 19:09:30 -0600
commit7232eddd2f7305f5f7908f1d449568bddf0506d8 (patch)
tree952ddc25dc01bfaca5f6da622df946dfb83c94a0
parentf658cd9051dcf73460125751b9f95bf41d0333c9 (diff)
parent9156303ac9e8f48f56a91d19a6d4747be6a6a946 (diff)
downloadpfsense-packages-7232eddd2f7305f5f7908f1d449568bddf0506d8.tar.gz
pfsense-packages-7232eddd2f7305f5f7908f1d449568bddf0506d8.tar.bz2
pfsense-packages-7232eddd2f7305f5f7908f1d449568bddf0506d8.zip
Merge pull request #1195 from jorgelustosa/patch-7
-rw-r--r--config/apache_mod_security-dev/apache_mod_security.template10
1 files changed, 5 insertions, 5 deletions
diff --git a/config/apache_mod_security-dev/apache_mod_security.template b/config/apache_mod_security-dev/apache_mod_security.template
index d004a9ae..2d63abbd 100644
--- a/config/apache_mod_security-dev/apache_mod_security.template
+++ b/config/apache_mod_security-dev/apache_mod_security.template
@@ -25,7 +25,7 @@ SecRequestBodyAccess On
# Initiate XML Processor in case of xml content-type
#
SecRule REQUEST_HEADERS:Content-Type "text/xml" \
- "phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML"
+ "id:20001,phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML"
# Maximum request body size we will accept for buffering. If you support
@@ -56,7 +56,7 @@ SecRequestBodyLimitAction Reject
# or log a high-severity alert (when deployed in detection-only mode).
#
SecRule REQBODY_ERROR "!@eq 0" \
-"phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"
+"id:20002,phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"
# By default be strict with what we accept in the multipart/form-data
# request body. If the rule below proves to be too strict for your
@@ -64,7 +64,7 @@ SecRule REQBODY_ERROR "!@eq 0" \
# _not_ to remove it altogether.
#
SecRule MULTIPART_STRICT_ERROR "!@eq 0" \
-"phase:2,t:none,log,deny,status:44,msg:'Multipart request body \
+"id:20003,phase:2,t:none,log,deny,status:44,msg:'Multipart request body \
failed strict validation: \
PE %{REQBODY_PROCESSOR_ERROR}, \
BQ %{MULTIPART_BOUNDARY_QUOTED}, \
@@ -81,7 +81,7 @@ IH %{MULTIPART_FILE_LIMIT_EXCEEDED}'"
# Did we see anything that might be a boundary?
#
SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \
-"phase:2,t:none,log,deny,status:44,msg:'Multipart parser detected a possible unmatched boundary.'"
+"id:20004,phase:2,t:none,log,deny,status:44,msg:'Multipart parser detected a possible unmatched boundary.'"
# PCRE Tuning
# We want to avoid a potential RegEx DoS condition
@@ -95,7 +95,7 @@ SecPcreMatchLimitRecursion 1000
# MSC_PCRE_LIMITS_EXCEEDED: PCRE match limits were exceeded.
#
SecRule TX:/^MSC_/ "!@streq 0" \
- "phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"
+ "id:20005,phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"
# -- Response body handling --------------------------------------------------