Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.0.1
-
None
Description
When doing a match-and-replace operation on the query string, the filter first checks if the query matches before allocating more memory to do the operation. Instead of interpreting only positive return values as matches, the matching code mistakenly interprets all non-zero return values as positive matches.