ModSecurity
ModSecurity copied to clipboard
ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. It has a robust event-based programming language which provides protection from a range o...
In the [v2 reference](https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-(v2.x)#REQUEST_BODY), the REQUEST_BODY variable info contains: > Holds the raw request body. This variable is available **only** if the URLENCODED request body processor was used, which will...
See #1996. Every commit has detailed description. I've implemented the fallback approach so far: if RE2 support is enabled, every regular expression is compiled with RE2, and if that fails,...
**Describe the bug** The [Base64DecodeExt](https://github.com/owasp-modsecurity/ModSecurity/wiki/Reference-Manual-(v3.x)#user-content-base64DecodeExt) item in the Reference Manual wiki page provide a link that isn't currently online now. I found a version on Internet Wayback machine, and so...
**Describe the bug** v3 appears to interpret `%` signs that aren't part of URI encoding in some way. The result is that on nginx with v3 the URI `/?test=%ua` produces...
This PR includes changes to support building libModSecurity v3 on Windows. Work was initially done on a snapshot of v3.0.12 to work on the latest stable version of the library,...
Introducing the use of assertions to address throw; calls that lack try-catch blocks. Upon examining the caller code that utilized methods containing the questioned throw; calls, it became clear that,...
This pull request fixes two memory leaks, reported by [SonarCloud](https://sonarcloud.io/project/issues?impactSoftwareQualities=RELIABILITY&resolved=false&id=owasp-modsecurity_ModSecurity). * [test/regression/regression.cc](https://sonarcloud.io/project/issues?impactSoftwareQualities=RELIABILITY&resolved=false&id=owasp-modsecurity_ModSecurity&open=AY1CfKEhrsSpWCKX0w7f) * [tools/rules-check/rules-check.cc](https://sonarcloud.io/project/issues?impactSoftwareQualities=RELIABILITY&resolved=false&id=owasp-modsecurity_ModSecurity&open=AY1CfKGQrsSpWCKX0xBV) None of them modified the library itself.
Added a design doc explaining the approach
This PR is the renewal and addition of the PR #1683, and solves #911. Example: ``` SecRule REQUEST_URI "@beginswith /index.php" "id:1001,phase:1,pass,nolog, ctl:ruleRemoveTargetById=942100;ARGS:/^password[\d+]$/" ``` The new patch works with PCRE2 too....
I would like to provide a log file separately for each user and their website. Is there a chance to do this using variables SecAuditLog?