#2192
ModSec version is 2.7.3 used with IBM HTTP server
We have a scenario.
We use configuration like below.
SecRule REMOTE_ADDR "@ipMatchFromFile /etc/opt/cpf/conf/modsecurity_whitelist" "id:250000004,phase:1,nolog,allow"
SecRule REMOTE_ADDR "@ipMatchFromFile /etc/opt/cpf/conf/modsecurity_whitelist" "id:250000005,phase:5,nolog,skipAfter:WHITELIST_NOLOG"
ISSUE:
When we whitelist an IPv6 address( in whitelist file the address is expanded), if a request then comes from a non expanded IPV6 address, it is not whit list it and mod_security blocks it.
Is this a known issue that is fixed in alter versions?
We don't have any logs for this since it is happening in a customer environment and we dont have many IPV6 test labs.
#2192
ModSec version is 2.7.3 used with IBM HTTP server
We have a scenario.
We use configuration like below.
SecRule REMOTE_ADDR "@ipMatchFromFile /etc/opt/cpf/conf/modsecurity_whitelist" "id:250000004,phase:1,nolog,allow"
SecRule REMOTE_ADDR "@ipMatchFromFile /etc/opt/cpf/conf/modsecurity_whitelist" "id:250000005,phase:5,nolog,skipAfter:WHITELIST_NOLOG"
ISSUE:
When we whitelist an IPv6 address( in whitelist file the address is expanded), if a request then comes from a non expanded IPV6 address, it is not whit list it and mod_security blocks it.
Is this a known issue that is fixed in alter versions?
We don't have any logs for this since it is happening in a customer environment and we dont have many IPV6 test labs.