> What CRS version are you using? > How do you have the SecRuleEngine configured? Unless it is set to On, you > can't rely upon returned status codes for detection. > How have you activated the rules? Are you sure you have the > modsecurity_crs_41_sql_injection_attacks.conf file activated? > > I tested your first payload against the latest CRS version and it > triggered many SQLi alerts -
sorry for the fuss, that is totally my fault not being aware of a broken symbolic linked file. well, that is an opportunity to check out the crc_2.2.4 on the way. thanks Ryan and keep up the good work! _______________________________________________ Owasp-modsecurity-core-rule-set mailing list Owasp-modsecurity-core-rule-set@lists.owasp.org https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set