Skip to content
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

user12986714: Watch ([\w.+-]{5,}+@[\w.+-]{3,}+)\W*+(?:\1\W*+){3,}+(?#repeated emails with no separation char. This regex can result in high CPU usage and is not O_n) #4272

Closed
wants to merge 1 commit into from

Conversation

SmokeDetector
Copy link
Member

user12986714 requests the watch of the watch_keyword ([\w.+-]{5,}+@[\w.+-]{3,}+)\W*+(?:\1\W*+){3,}+(?#repeated emails with no separation char. This regex can result in high CPU usage and is not O_n). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

…ted emails with no separation char. This regex can result in high CPU usage and is not O_n)` by user12986714
@metasmoke
Copy link
Contributor

([\w.+-]{5,}+@[\w.+-]{3,}+)\W*+(?:\1\W*+){3,}+(?#repeated emails with no separation char. This regex can result in high CPU usage and is not O_n) has been seen in 12 true positives, 0 false positives, and 1 NAA.

@SmokeDetector
Copy link
Member Author

Rejected by Daniil in Charcoal HQ. Reason: 'his regex can result in high CPU usage, all tp's caught by other reasons'

Rejected with SmokeyReject

@SmokeDetector SmokeDetector deleted the auto-blacklist-1596157274 branch August 12, 2020 19:54
@SmokeDetector
Copy link
Member Author

Rejected by Daniil in Charcoal HQ. Reason: 'This regex can result in high CPU usage, all tp's caught by other reasons'

Rejected with SmokeyReject

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants