[
https://www.modsecurity.org/tracker/browse/CORERULES-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Barnett resolved CORERULES-48.
-----------------------------------
Resolution: Fixed
> bug in setting anomaly value
> ----------------------------
>
> Key: CORERULES-48
> URL: https://www.modsecurity.org/tracker/browse/CORERULES-48
> Project: Core Rules
> Issue Type: Bug
> Security Level: Normal
> Components: Configuration
> Affects Versions: 2.0.7
> Environment: CentOS 5.5, httpd-2.2.3-43.el5.centos,
> mod_security-2.5.12-1.el5, CRS 2.0.7
> Reporter: brian roller
> Assignee: Ryan Barnett
>
> Most (if not all) of the rules in modsecurity_crs_41_phpids_filters.conf
> appear to be attempting to modify the anomaly score with
> "setvar:%{tx.critical_anomaly_score}". Presumably this should be something
> like "setvar:tx.anomaly_score=+%{tx.critical_anomaly_score}"?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://www.modsecurity.org/tracker/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
[email protected]
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
