-
-
Notifications
You must be signed in to change notification settings - Fork 402
RCE detection bypass at PL1 #1513
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
User franbuehler commented on date 2019-08-19 07:34:37: First command gets the following scores: Second command: |
User marcstern commented on date 2019-08-20 06:30:12: This evasion technique (and several others) can be defeated with the t:bash transformation - see https://www.approach.be/en/modsecurity.html |
User dune73 commented on date 2019-08-20 06:38:17: If only it would be merged ... |
User theMiddleBlue commented on date 2019-09-07 00:05:37: IIRC we already talk about that in a meeting (refer to https://www.secjuice.com/web-application-firewall-waf-evasion/). If you agree, I would try to catch this bypass technique in PL1. |
User github-actions[bot] commented on date 2020-02-19 00:02:20: This issue has been open 120 days with no activity. Remove the stale label or comment, or this will be closed in 14 days |
User theMiddleBlue commented on date 2020-02-24 13:47:01: still in progress... |
replaced by #1783 |
Issue originally created by user dune73 on date 2019-08-19 07:06:16.
Link to original issue: SpiderLabs/owasp-modsecurity-crs#1513.
The following bypass was pasted on twitter.
https://twitter.com/spyerror/status/1162826904833089541?s=19
According to franbuehler, this passes on PL1, but is being detected on PL2.
Type of Issue
RCE rule detection bypass
Description
See above.
Your Environment
CRS 3.1
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: