owasp-modsecurity / owasp-modsecurity/ModSecurity
rx: regex error 'MATCH_LIMIT' for pattern
Open
Nobody has claimed this yet.
3.x
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Describe the bug
I don't see any real problem just noticed logs entries.
Logs and dumps
SecDebugLog & SecDebugLogLevel 3
[172440041140.141021]` [/vystrelovaci-rukavice-3-sipky/] [1] rx: regex error 'MATCH_LIMIT' for pattern '[\"'`][\[\{].*[\]\}][\"'`].*(::.*jsonb?)?.*(?:(?:@|->?)>|<@|\?[&\|]?|#>>?|[<>]|<-)|(?:(?:@|->?)>|<@|\?[&\|]?|#>>?|[<>]|<-)[\"'`][\[\{].*[\]\}][\"'`]|json_extract.*\(.*\)
Server:
- ModSecurity version (and connector): libmodsecurity 3.0.12 & lattest nginx-connector
- WebServer: nginx 1.27.1
- OS (and distro): Oracle Linux 8.10 x86_64
Rule Set:
- CRS v4.5.0
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
No source files or tests are named. Start by reproducing the logged MATCH_LIMIT message with libmodsecurity 3.0.12, the nginx connector, nginx 1.27.1, and CRS 4.5.0, then trace the regex evaluation path; done means the cause is identified and the reported behavior is addressed with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nginx
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100