owasp-modsecurity / owasp-modsecurity/ModSecurity
Memory Leak with nginx 1.26
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Describe the bug
I using modsecurity v3.0.13 with nginx 1.26. After running one day, memory over to 90%.
I using valgrind monitor memory. Below log of valgrind:
==300601== LEAK SUMMARY:
==300601== definitely lost: 1,024 bytes in 1 blocks
==300601== indirectly lost: 0 bytes in 0 blocks
==300601== possibly lost: 0 bytes in 0 blocks
==300601== still reachable: 21,007 bytes in 444 blocks
==300601== suppressed: 0 bytes in 0 blocks
Can you help me?
Thanks
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 reproducing the report with ModSecurity v3.0.13 and nginx 1.26 under Valgrind, using the one-day runtime described in the issue. The Valgrind leak summary is the only diagnostic supplied; done requires identifying the leak's cause and demonstrating that the memory growth or reported leak no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nginx
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100