Open lc4nt opened 6 years ago
To be clear, this is not a problem with the regexp type only. Any observable type is applied the same sanitization process, whether it makes sense or not.
Is there any update or work around to this feature? I currently have a custom observable that contains a link I do NOT want to be sanitized.
As reported by @rolinh all observable are sanitized. With this mode analyzer does not able to run over it. Any update or work around?
Many thanks
Request Type
Bug
Work Environment
Problem Description
When creating a regular expression type of observable
regexp
, the dots are sanitized in an attempt to make potential link unclickable, as well as anyhttps
orhttp
string. But this invalidates the regular expression itself.Steps to Reproduce
^https?:\/\/.+/myevilpattern\?evilfile\.php$
^hxxps?:\/\/[.]+/myevilpattern\?evilfile\[.]php$
. The brackets andhxxps
are making the regular expression different from the original.Possible Solutions
Avoid sanitizing the
regexp
observable like if it contains a URL.