You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the first of the two, there are more than a few places in v2 where a (freakishly unlikely) failure to allocate memory from a memory pool is not checked. These could perhaps be best handled en masse at some point.
Regarding the second item, just to expand on it a little:
the problem input is expressly not supported; although the rx operator is implied in a SecRule directive if an operator is absent, the same is not true for SecConnReadStateLimit. Indeed, the documentation expressly states which three operators are supported and it is only the three (ipMatch, ipMatchF and ipMatchFromFile
the failure occurs on startup rather than while running
That doesn't mean this second issue shouldn't be fixed. If an admin creates such an erroneous entry, diagnosing the problem is not at all friendly. I'll tentatively plan to include this in the next 2.9.x release.
First problem (quite unusual, I admit):
config_orig_path can be NULL, so
Second problem (I found it in prod, difficult to troubleshoot):
In case we use the SecConnReadStateLimit diective without operator (only a regex), paparm is NULL => memory fault, crash without any message.
Fix:
The text was updated successfully, but these errors were encountered: