Vulnerable regexp in rule 932140
See original GitHub issue_Issue originally created by user s0md3v on date 2019-04-15 16:03:37. Link to original issue: https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1354._
The vulnerable regular expression is located in
/crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf
on line 404. [Link]
The vulnerability is caused by nested repetition operators and can be exploited with the following string
for/d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d//d/ %x in(x) dx
Issue Analytics
- State:
- Created 3 years ago
- Comments:13
Top Results From Across the Web
Regular expression Denial of Service - ReDoS
Regular expression Denial of Service - ReDoS on the main website for The OWASP ... the attacker can assume the same vulnerable Regex...
Read more >REQUEST-932-APPLICATION-ATTACK-RCE.conf - 3.1.1 vs ...
# This rule detects Unix command injections. # This rule detects Unix command injections. # A command injection takes a form such as:...
Read more >The Regular Expression Denial of Service (ReDoS) cheat-sheet
This post is intended as a “technical two-pager” to summarize a security vulnerability called Regex-based Denial of Service (AKA Regex DoS, ...
Read more >Core Rule Set Inventory – Welcome to netnea
Rule ID Paranoia Level Severity
901001 PL1 none
901450 PL1 none
905100 PL1 none
Read more >how can a regular expression cause a ReDoS vulnerability?
Catastrophic backtracking: real examples. Let's inspect several regular expressions for vulnerabilities. I wrote a small program — it displays a ...
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
User fgsch commented on date 2019-05-03 23:07:24:
We should correct the regexp regardless since the parameter can only appear once. I’ve commented on the PR, and hopefully after it’s updated we can merge it if there are no objections.
User fgsch commented on date 2019-04-26 21:04:41:
From pcre: