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.

Sign up for GitHub

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

Jump to bottom

Upgrade to OWASP >= 1.2 #4757

Closed
bazalt opened this issue Nov 16, 2019 · 0 comments · Fixed by #4829
Closed

Upgrade to OWASP >= 1.2 #4757

bazalt opened this issue Nov 16, 2019 · 0 comments · Fixed by #4829

Comments

@bazalt
Copy link

bazalt commented Nov 16, 2019

Is this a request for help? no

What keywords did you search in NGINX Ingress controller issues before filing this one? : owasp, crs

Is this a BUG REPORT or FEATURE REQUEST?: FEATURE

Upgrade OWASP to version >= 1.2. This would avoid false-positives when using WordPress Gutenberg editor.
See Gutenberg rules on https://github.com/SpiderLabs/owasp-modsecurity-crs/blob/v3.2/master/rules/REQUEST-903.9002-WORDPRESS-EXCLUSION-RULES.conf

NGINX Ingress controller version:
1.26

What happened:
Users face false-positives while manipulating posts with Gutenberg editor.

What you expected to happen:
No error while editing posts in WordPress

How to reproduce it (as minimally and precisely as possible):
WordPress >= 5.0 under Ingress-Nginx <= 0.26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update modsecurity crs to v3.2.0 aledbf/ingress-nginx
1 participant
@bazalt