Re: ModSecurity mod_security-2.9.2, Apache 2.4, oswap crs

"Madden, Joe via mod-security-users" <[email protected]>
Newsgroups gmane.comp.apache.mod-security.user
Message-ID <LNXP123MB191465866143AC44BA2924DD919E0@LNXP123MB1914.GBRP123.PROD.OUTLOOK.COM>
Hi Ervin,

This information worked perfectly after I put the rules within the modsecurity_crs_10_config.conf

Thanks

Joe.

-----Original Message-----
From: Ervin Hegedüs <[email protected]> 
Sent: 03 October 2019 16:33
To: Madden, Joe via mod-security-users <[email protected]>
Cc: Madden, Joe <[email protected]>
Subject: Re: [mod-security-users] ModSecurity mod_security-2.9.2, Apache 2.4, oswap crs

Hi Madden,

On Thu, Oct 03, 2019 at 02:43:45PM +0000, Madden, Joe via mod-security-users wrote:
> Hi all,
> 
> I've got an issue where a password field with complex characters was triggering the following:
> 
...
 
> I added this into the virtual host configuration (and tried the crs-setup.conf) but it doesn't exclude the password field.
> 
>       SecRule REQUEST_URI "@beginsWith /webclient/login" \
>               "phase:2,nolog,pass,id:10001,ctl:ruleRemoveTargetById=981173;ARGS:password"
> 
> 
> Can anyone tell me why?

I think your custom rule in vhost context exists later than the target rule.

ModSecurity *have to* know the exclusions before the rule activated.

> What is the correct way to exclude this from that specific field (and 
> not all other fields on the URL)

try to write a chained rule to the global exclusions list:

SecRule REMOTE_HOST "www\.yourhost\.com" \
    "phase:2,nolog,pass,id:10001,chain"
    SecRule ... like above without phase, pass and id



a.
 

_______________________________________________
mod-security-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mod-security-users
Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs:
http://www.modsecurity.org/projects/commercial/rules/
http://www.modsecurity.org/projects/commercial/support/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.