Closed kearva closed 11 years ago
Yes. We expected to see false-positives with this flag. However this is necessary since we had cases where people try to attack Apps sending SQLi data inside the filename=.
We cannot remove this checking because the multipart code is not being checked by RuleEngine. This is work mod_security was designed. You could try add some exceptions to work with this false-positive.
I'm adding new variables MULTIPART_FILENAME and MULTIPART_NAME. I think we can update the CRS to use those variables and remove this checking in the future
Done. However before remove this checking we must update CRS and see if the rules will do the job. I will check with Ryan (CRS lead) if he can update it for 2.7.3 or not.
validate_quotes in apache2/msc_multipart.c will set flag_invalid_quoting if a filename contains a single quote.
A request with the following header will set the flag_invalid_quoting.
Content-Disposition: form-data; name="userfile"; filename="AS'4360.pdf"
This is header is correct and valid according to RFC 2045, RFC 2183 and RFC 822.