Changes the default configuration to mimic v2 behavior on multipart

Further info on: #1747, #1924
This commit is contained in:
Felipe Zimmerle 2018-11-01 18:00:12 -03:00
parent 31c8d4c520
commit 9ada0a28c8
No known key found for this signature in database
GPG Key ID: E6DFB08CE8B11277
2 changed files with 7 additions and 5 deletions

View File

@ -88,7 +88,7 @@ v3.0.3 - YYYY-MMM-DD (to be released)
- Fixed LMDB collection errors - Fixed LMDB collection errors
[Issue #1787 - @airween, @zimmerle] [Issue #1787 - @airween, @zimmerle]
- Fixed false positive MULTIPART_UNMATCHED_BOUNDARY errors - Fixed false positive MULTIPART_UNMATCHED_BOUNDARY errors
[Issue #1747 - @airween] [Issue #1747, #1924 - @airween, @victorhora, @defanator, @zimmerle]
- Fix ip tree lookup on netmask content - Fix ip tree lookup on netmask content
[Issue #1793 - @tinselcity, @zimmerle] [Issue #1793 - @tinselcity, @zimmerle]
- Changes the behavior of the default sec actions - Changes the behavior of the default sec actions

View File

@ -114,10 +114,12 @@ FL %{MULTIPART_FILE_LIMIT_EXCEEDED}'"
# allowed. # allowed.
# #
SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \ #
"id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'" # See #1747 and #1924 for further information on the possible values for
#SecRule MULTIPART_UNMATCHED_BOUNDARY "@eq 1" \ # MULTIPART_UNMATCHED_BOUNDARY.
#"id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'" #
SecRule MULTIPART_UNMATCHED_BOUNDARY "@eq 1" \
"id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"
# PCRE Tuning # PCRE Tuning