-
Notifications
You must be signed in to change notification settings - Fork 1.6k
PCRE limit exceeded #1176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @quenenni, Are you running Apache altogether with PHP and ModSecurity ? Do you mind to share your ModSecurity's initialization lines? You can find those in your error log, just after restart the server. |
@zimmerle : of course, all you need.. Yes, Apache / Php & Modsec.
If you need more infos, don't hesitate to ask. Thanks |
I noticed that our PCRE version (libpcre3) is quite old (v8.30 - 2012-02-04). If it's indeed the case, libpcre3 too old, well, we'll do with it. Thanks |
Hi @quenenni, The old version of pcre should not be a problem, I was more concerned about a version mismatch. In case of a version mismatch (Apache and ModSecurity using different versions) weird behavior is expected. ModSecurity shares the Apache memory space with every other modules, so it is possible that a second module is reducing the PCRE limits. It worth to check. |
Server: Debian Wheezy
libapache2-mod-security2: v2.8.0-2~bpo70+1
modsec rules: v3
On our new server, with for the moment only few low traffic websites, I have lots of "PCRE limits exceeded".
On our old server, I thought it normal as it was not a powerful one anymore and lots of websites on it.
But here, I wonder why I have so many.
I already updated the directives SecPcreMatchLimit & SecPcreMatchLimitRecursion to 2000 to see if there is a difference.
And I'm afraid that it will become a problem later when all the websites will have been migrated on this new server.
The rules that generate these PCRE errors are:
(between () is the number of times for each)
Can I change the directives SecPcreMatchLimit & SecPcreMatchLimitRecursion to a higher number?
Won't be that a problem for performances later when the server will have plenty of websites?
Is there any other variable I can play with?
I attached modsec logs for each of these errors.
PCRE-REQUEST-41-APPLICATION-ATTACK-XSS.txt
PCRE-REQUEST-42-APPLICATION-ATTACK-SQLI.txt
PCRE-RESPONSE-51-DATA-LEAKAGES-SQL.txt
The text was updated successfully, but these errors were encountered: