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
{{ message }}
This repository has been archived by the owner on Dec 15, 2023. It is now read-only.
In the modify_message function, when dynamically generating the regex value, special characters are not escaped if they're part of a named group (?P<{}>{}). When executing "match_exp = re_compile(exp + groups_exp)", groups_exp may contain special that will either generate an error or unexpected behavior.
Workaround:
In my case I was extracting a string that sometimes contains a + (base64-ish) with the following regex "token": "(?P<token>[^"]+).
I substituted lines 462, 463
This workaround only fixed my case (+ char in extracted group), groups_exp should be properly escaped for all regex special characters before being recompiled.
Edit: workaround was not so clear.
The text was updated successfully, but these errors were encountered:
In the modify_message function, when dynamically generating the regex value, special characters are not escaped if they're part of a named group (?P<{}>{}). When executing "match_exp = re_compile(exp + groups_exp)", groups_exp may contain special that will either generate an error or unexpected behavior.
Workaround:
In my case I was extracting a string that sometimes contains a + (base64-ish) with the following regex
"token": "(?P<token>[^"]+)
.I substituted lines 462, 463
with
This workaround only fixed my case (+ char in extracted group), groups_exp should be properly escaped for all regex special characters before being recompiled.
Edit: workaround was not so clear.
The text was updated successfully, but these errors were encountered: