Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When receiving requests quickly or concurrently, mod_security is unable to keep accurate count.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
Here is configuration for reproducing:
SecRuleEngine On
SecRule REQUEST_COOKIES:SESSIONID !^$ phase:1,id:118,nolog,pass,setsid:%{REQUEST_COOKIES.SESSIONID}
SecAction phase:1,id:119,nolog,pass,setvar:SESSION.my_counter=+1
And here is a test script:
for i in $(seq 1 1000); do
curl -b "SESSIONID=testing" localhost &> /dev/null &
done
Actual results: Major loss in counter increments. You can check using modsec-sdbm-util and looking at the my_counter variable in output.
Expected results: No loss in counter increments.
Additional info: A solution has been proprosed upstream (https://github.com/SpiderLabs/ModSecurity/pull/1224) and is planned to be included in JBCS distribution of mod_security (https://issues.jboss.org/browse/JBCS-231).
Description of problem: When receiving requests quickly or concurrently, mod_security is unable to keep accurate count. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Here is configuration for reproducing: SecRuleEngine On SecRule REQUEST_COOKIES:SESSIONID !^$ phase:1,id:118,nolog,pass,setsid:%{REQUEST_COOKIES.SESSIONID} SecAction phase:1,id:119,nolog,pass,setvar:SESSION.my_counter=+1 And here is a test script: for i in $(seq 1 1000); do curl -b "SESSIONID=testing" localhost &> /dev/null & done Actual results: Major loss in counter increments. You can check using modsec-sdbm-util and looking at the my_counter variable in output. Expected results: No loss in counter increments. Additional info: A solution has been proprosed upstream (https://github.com/SpiderLabs/ModSecurity/pull/1224) and is planned to be included in JBCS distribution of mod_security (https://issues.jboss.org/browse/JBCS-231).