owasp-modsecurity / owasp-modsecurity/ModSecurity
Ability to set msg in subsequent chained rules
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Currenlty, the msg can be set only by the starting SecRule statement in a chained rule which is often configured to work in phase 1 and no other information is available in here other than HTTP headers. For example, there is no way to log POST_VARS to the log message if the first rule operates in phase 1.
It is suggested to either make the msg be set by any SecRule in a chained rule or have the ability to edit the contents of msg.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how SecRule chains handle the msg value across phases, with attention to phase 1 rules and POST_VARS availability. Determine whether chained rules can safely replace or edit the message, and verify that the resulting log message includes the later rule's information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100