higress-group/higress

Upgrade the WAF plugin's CRS rule version to the latest

Open

#1,620 opened on Dec 23, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
help wantedlevel/normalsig/wasm

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

          Currently, the owasp 4.0.0-rc1 rule engine is being used. We will upgrade to the latest version later. For now, we can bypass it like this:
  1. Configure an independent waf plugin configuration for this route
  2. In secRules, configure SecRuleRemoveById 932250 to remove this problematic rule

Originally posted by @johnlanni in https://github.com/alibaba/higress/issues/1619#issuecomment-2559581637

Contributor guide

Research direction
Investigate the current CRS rule version used in the WAF plugin, find the latest release of OWASP CRS, and implement the upgrade by updating the rule files or configuration, ensuring compatibility with existing rules.
Tech stack
go
Domain
securitybackend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60