easyapache, mod_sec 2.7 and MULTIPART_STRICT_ERROR

sebby

• November 08, 2013 15:13

Hello everyone, EasyApache recently started injecting the following patch to ModSecurity 2.7: SecRule MULTIPART_STRICT_ERROR "!@eq 0" "phase:2,t:none,log,deny,status:44,msg:'Multipart request body failed strict validation: PE %{REQBODY_PROCESSOR_ERROR}, BQ %{MULTIPART_BOUNDARY_QUOTED}, BW %{MULTIPART_BOUNDARY_WHITESPACE}, DB %{MULTIPART_DATA_BEFORE}, DA %{MULTIPART_DATA_AFTER}, HF %{MULTIPART_HEADER_FOLDING}, LF %{MULTIPART_LF_LINE}, SM %{MULTIPART_MISSING_SEMICOLON}, IQ %{MULTIPART_INVALID_QUOTING}, IP %{MULTIPART_INVALID_PART}, IH %{MULTIPART_INVALID_HEADER_FOLDING}, FL %{MULTIPART_FILE_LIMIT_EXCEEDED}',id:1234123456"
When this rule was implemented, many clients complained about false positives triggered by the IQ segment (MULTIPART_INVALID_QUOTING). I would like to avoid whitelisting the whole rule and would prefer skipping only the IQ test. I have two questions:

]
• How to edit this rule to skip the IQ part.
• How should I override this rule (not in modsec2.conf obviously because it will be overwritten by easyapache on next run).

I thank you in advance for your assistance. Kind Regards, Seb Also on this topic: -

• 

  quizknows

  • November 08, 2013 22:05

  I would honestly try just removing the "IQ %{MULTIPART_INVALID_QUOTING}," part from modsec2.conf, then run an EA and see if it reverts it. If it does revert, you could make a custom hook to "Fix" the file after EA runs. Otherwise, the easiest way to whitelist would be by script file name in modsec2.user.conf or other includes file. Say it's tripping on someones site "submit.php" file, then add this: SecRuleRemoveById 1234123456 That would whitelist all checks from the multipart rule on that particular filename, but it's better than whitelisting it completely for the server or domain.

  0
• 

  cPanelMichael

  • November 11, 2013 12:12

  Hello :) You could also utilize a third-party utility such as ConfigServer ModSecurity Control that makes it easier to manage the Mod_Security rules. Thank you.

  0
• 

  sebby

  • November 11, 2013 14:30

  Hi, I already tried removing the "IQ %{MULTIPART_INVALID_QUOTING}," part from modsec2.conf but it doesn't work. The legitimate scripts were still blocked. I think that this particular string is there only for verbose mod_sec reporting/logs (i.e. explain why the rule was triggered). I am already using ConfigServer ModSecurity Control and used it to whitelist the complete rule server wide while I find a solution. So again may question is: Is there a way to skip the IQ test? Kind Regards, Seb

  0
• 

  quizknows

  • November 11, 2013 16:10

  Did you restart apache after modifying the rule? Otherwise your change was not active.

  0
• 

  sebby

  • November 12, 2013 00:19

  [quote="quizknows, post: 1504581">Did you restart apache after modifying the rule? Otherwise your change was not active.
  Yes I did.

  0
• 

  quizknows

  • November 12, 2013 01:00

  I'd check the modsec audit log for further information at that point.

  0

Please sign in to leave a comment.