Windows下Apache ModSecurity配置暴力防护提示集合不存在如何解决
错误根因
报错核心原因是USER、IP两个ModSecurity持久化集合没有提前初始化:
你当前配置中,只有请求携带符合规则的Authorization认证头时,才会通过initcol指令初始化这两个集合。当请求没有带符合要求的认证头、触发401响应时,直接操作不存在的集合就会抛出该错误。
另外你现有配置存在语法逻辑错误:ID为2000015的规则使用了chain链式匹配修饰符,但后面只跟了1条SecAction,链式匹配要求至少2条规则同时满足才会执行后续动作,这条规则的逻辑本身就不会生效。
修复步骤
1. 全局初始化IP集合
IP集合不依赖认证信息,所有请求都可以提前初始化,避免IP集合不存在的报错,在配置最开头添加如下规则:
# 全局初始化IP集合,phase1最早阶段执行 SecAction "id:2000001,phase:1,pass,nolog,initcol:IP=%{REMOTE_ADDR}"
2. 修正401计数规则的逻辑
去掉错误的chain修饰,增加USER集合存在性判断,不存在时先初始化再更新计数:
SecRule RESPONSE_STATUS "401" \ "phase:5,pass,id:2000015,logdata:'basic auth de @%{IP}, var: %{IP.begin}, user: %{USER.name}, ufc: %{USER.user_false_counter}, block: %{USER.bf_block}, IPblock: %{IP.bf_block}, ifc: %{IP.ip_false_counter}'" # 先更新IP计数(已经提前初始化肯定存在) SecAction "setvar:IP.ip_false_counter=+1,expirevar:IP.ip_false_counter=300" # 判断USER集合存在时再更新USER计数,不存在则跳过 SecRule &USER:name "@gt 0" \ "chain,pass,nolog" SecAction "setvar:USER.user_false_counter=+1,expirevar:USER.user_false_counter=300"
3. 给所有USER相关的规则增加存在性判断
所有操作USER集合的规则都先判断集合是否存在,避免无认证头请求触发报错:
# 原有用户拦截规则增加存在判断 SecRule &USER:bf_block "@gt 0" \ "chain,id:'2000005',phase:4,deny,logdata:'Access denied [by USER] IP: @%{REMOTE_ADDR}, user: %{USER.name}'" SecRule USER:bf_block "@eq 1" # 原有用户计数阈值判断增加存在判断 SecRule &USER:user_false_counter "@gt 0" \ "chain,id:'2000020',phase:3,t:none,pass,setvar:USER.bf_block,setvar:!USER.user_false_counter,expirevar:USER.bf_block=30" SecRule USER:user_false_counter "@ge 2"
修复后完整配置示例
SecStatusEngine On # 新增:全局初始化IP集合 SecAction "id:2000001,phase:1,pass,nolog,initcol:IP=%{REMOTE_ADDR}" # IP拦截规则(IP已提前初始化无需额外判断) SecRule IP:bf_block "@eq 1" \ "id:'2000004',phase:4,deny,logdata:'Access denied [by IP] IP: @%{REMOTE_ADDR}, user: %{USER.name}'" # 修正后用户拦截规则 SecRule &USER:bf_block "@gt 0" \ "chain,id:'2000005',phase:4,deny,logdata:'Access denied [by USER] IP: @%{REMOTE_ADDR}, user: %{USER.name}'" SecRule USER:bf_block "@eq 1" # 原有认证头解析规则不变 SecRule REQUEST_HEADERS:authorization "Basic ([a-zA-Z0-9]+=*)$" "phase:3,nolog,pass,id:2000012,chain,capture" SecRule TX:1 "^([-a-zA-Z0-9_]+):" "t:base64Decode,chain,capture" SecAction initcol:USER=%{TX.1},setvar:USER.name=%{TX.1} # 修正后401计数规则 SecRule RESPONSE_STATUS "401" \ "phase:5,pass,id:2000015,logdata:'basic auth de @%{IP}, var: %{IP.begin}, user: %{USER.name}, ufc: %{USER.user_false_counter}, block: %{USER.bf_block}, IPblock: %{IP.bf_block}, ifc: %{IP.ip_false_counter}'" SecAction "setvar:IP.ip_false_counter=+1,expirevar:IP.ip_false_counter=300" SecRule &USER:name "@gt 0" \ "chain,pass,nolog" SecAction "setvar:USER.user_false_counter=+1,expirevar:USER.user_false_counter=300" # 修正后用户失败次数阈值规则 SecRule &USER:user_false_counter "@gt 0" \ "chain,id:'2000020',phase:3,t:none,pass,setvar:USER.bf_block,setvar:!USER.user_false_counter,expirevar:USER.bf_block=30" SecRule USER:user_false_counter "@ge 2" # IP失败次数阈值规则(IP已提前初始化无需额外判断) SecRule IP:ip_false_counter "@ge 2" \ "id:'2000021',phase:3,pass,t:none,setvar:IP.bf_block,setvar:!IP.ip_false_counter,expirevar:IP.bf_block=300"
内容的提问来源于stack exchange,提问作者Gajanana
相关产品推荐
相关产品推荐

