8000 Correct Rule ID typos: 920120 to 930120 and 920121 to 930121 in REQUE… by 53cur3M3 · Pull Request #2263 · coreruleset/coreruleset · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Correct Rule ID typos: 920120 to 930120 and 920121 to 930121 in REQUE… #2263

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

Merged
merged 1 commit into from
Oct 29, 2021
Merged

Correct Rule ID typos: 920120 to 930120 and 920121 to 930121 in REQUE… #2263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions rules/REQUEST-930-APPLICATION-ATTACK-LFI.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,8 +118,8 @@ SecRule REQUEST_URI|ARGS|REQUEST_HEADERS|!REQUEST_HEADERS:Referer|XML:/* "@rx (?
# MATCHED_VAR in logdata and that variable points to the infos from the last
# chained rule.
#
# 920120 OS Files Access check for ARGS
# 920121 OS Files Access check for REQUEST_COOKIES and XML (stricter sibling)
# 930120 OS Files Access check for ARGS
# 930121 OS Files Access check for REQUEST_COOKIES and XML (stricter sibling)
#
# Check for Google OAuth2 callback must be in the chained rule, otherwise this
# rule cannot be excluded using exclusion rule (because of the way how ModSecurity
Expand Down
0