Very large amount of false positives with rule 932200
See original GitHub issueDescription
Rule 932200 is generating very high level of false positives on real world traffic.
Here are some of the examples I found after running it for a few hours:
https://website/bla/grille?jour= 4
<a href='https://newswebsite/article.html'>someone's name</a>
{"$productid":"4242"}
I have not dug enough to determine if this is a bug in the regex or just a FP prone strategy. Considering that it triggers a lot (on purpose?) on fairly common patterns, does it belong in PL1?
Confirmation
[X] I have removed any personal data (email addresses, IP addresses, passwords, domain names) from any logs posted.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Potential for False Positive Results with Antigen Tests ... - FDA
Laboratories should expect some false positive results when screening large populations with a low prevalence of COVID-19 infection.
Read more >The impact of false positive COVID-19 results in an area of low ...
KEYWORDS: COVID-19, false positive results, high prevalence, low prevalence ... in a very low prevalence setting, the negative predictive value was 100% (no ......
Read more >What are False Positives? | Dow Jones Professional
A “false positive” is an error in reporting which incorrectly indicates a match. To follow “Know Your Customer” (KYC) regulations, firms must conduct ......
Read more >Intrusion Detection - OWASP Foundation
An IDS, on the other hand, will only notify on the false positive and will not ... false negatives), produce an extremely large...
Read more >False-Positive HIV Test Results | CDC
Generally, HIV tests have high specificity, meaning that there are few false-positive results and most uninfected.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey, my apologies for the delayed response. At the time of 1820, our runtime didn’t actually support
MATCHED_VAR
but combined with 1831, the issue can be closed on my end. I’ll run more tests in the future and depending of what they show, I’ll open a new, more specific issue 😃Do you have any updates on this, @Taiki-San? In PR #1820 the rule has been fixed and additionally in PR #1831 the rule has been moved to PL2. We would like to hear your feedback so that we can properly close this issue.