-
-
Notifications
You must be signed in to change notification settings - Fork 402
Lots of false positives with 932236 #3220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for your report and sorry that you have issues with the rule.
If you all agree, I can open a PR for that. |
I'd be careful with the word boundary. It might be better to adjust the internal matching logic there. |
Not sure I follow you @theseion. What is the problem with the word boundary in this regex? Do we have shell command name substrings in the list? |
Some of the words are already being matched with logic that requires some specific token to follow the word. Simply adding a word boundary match would
This is like using a single screw driver for two sizes of screws. |
Got you. Thanks. Do you have a proposal with adjusting the internal matching logic? |
I suggest we run the list through the english word filter ( |
Result of extended spell.sh:
Ah, some of the commands in those 2 files are already extended with a This means, I have to take the original list (without the Does this sound like a good plan? |
Yes. Why are there weird words in the output from Also, see the PR I just opened: #3238. |
New output when using PR in #3238: $ ./spell.sh ../../regex-assembly/include/unix-shell-upto3-with-params.ra
-> checking unix-shell-upto3-with-params.ra
`- found English word: apt
`- found English word: ash
`- found English word: dig
`- found English word: ls
`- found English word: rev
`- found English word: tee
`- found English word: top
`- found English word: who
`- found English word: yum
`- found English word: zip
$ ./spell.sh ../../regex-assembly/include/unix-shell-4andup-with-params.ra
-> checking unix-shell-4andup-with-params.ra
`- found English word: bash
`- found English word: builtin
`- found English word: composer
`- found English word: curl
`- found English word: emacs
`- found English word: function
`- found English word: gawk
`- found English word: hostname
`- found English word: ispell
`- found English word: mail
`- found English word: nroff
`- found English word: perms
`- found English word: sendmail
`- found English word: shell
`- found English word: strings
`- found English word: task
`- found English word: telnet
`- found English word: troff
`- found English word: uncompress
`- found English word: unzip
`- found English word: volatility
`- found English word: xterm
`- found English word: yarn
So the situation improved when compared to above. |
I'll work on this after my vacation... |
Description
Rule 932236 is triggered frequently when using words like
mail
ortasks
mixed in with capital letters, spaces, or numbers. for example:MailerUI
tasksListView
I've tuned away this false positive but this rule is too aggressive in my opinion, at least for PL-2.
How to reproduce the misbehavior (-> curl call)
curl https://example.com/?args=MailerUI
curl https://example.com/?args=tasksListView
Logs
Your Environment
Confirmation
[X] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.
The text was updated successfully, but these errors were encountered: