This plugin contains rule exclusions for Nextcloud, a productivity platform and file hosting service. These rule exclusions are designed to resolve common false positives and allow for easier integration with the OWASP CRS (CRS).
Due to how feature rich Nextcloud is, not all apps in Nextcloud can be supported (Especially 3rd party apps). False positives that are due to unsupported apps within Nextcloud must be resolved by a custom rule exclusion.
Additional apps may be supported if there is enough demand from the community, but in general, support for apps made by 3rd parties (not Nextcloud) won't be added.
App Name | Status |
---|---|
Nextcloud Files | Supported ✅ |
Nextcloud Photos | Supported ✅ |
Nextcloud Calendar | Supported ✅ |
Nextcloud Contacts | Supported ✅ |
Nextcloud Teams (Formerly Circles) | Supported ✅ |
Nextcloud Mail | Supported ✅ |
Nextcloud Deck | Supported ✅ |
Nextcloud Office | Supported ✅ |
Nextcloud Notes | Supported ✅ |
Nextcloud Text Editor | Supported ✅ |
Nextcloud Recognize | Supported ✅ |
Nextcloud Cookbook | Supported ✅ |
Nextcloud Files HPB (Notify_Push) | Supported ✅ |
Nextcloud News | Supported ✅ |
Nextcloud Talk | Not supported ❌ |
Nextcloud Forms | Not supported ❌ |
Nextcloud Polls | Not supported ❌ |
Nextcloud Unspash | Not supported ❌ |
Nextcloud Collectives | Not supported ❌ |
Nextcloud Maps | Not supported ❌ |
Cospend | Not supported ❌ |
Breeze Dark | Not supported ❌ |
OnlyOffice | Not supported ❌ |
Nextcloud Tables | Not supported ❌ |
Nextcloud Assistant | Not supported ❌ |
ownCloud Music | Not supported ❌ |
For full and up to date instructions for the different available plugin installation methods, refer to How to Install a Plugin in the official CRS documentation.
For full and up to date instructions on how to conditionally enable/disable this plugin on a multisite environment, please refer to Conditionally enable plugins for multi-application environments in the official CRS documentation.
Due to some engine limitations, there are a few issues that can't be handled out of the box with this plugin (such as issues relating to uploading large file sizes). Below you can find a list of known limitations along with workarounds for this issue.
ModSecurity has very strict defaults on the size of file uploads (13MB), which is often too small even for photos.
It's strongly recommended to increase the max upload size to a value like 10GB by adjusting both SecRequestBodyNoFilesLimit
and SecRequestBodyLimit
.
The process of increasing the value is slightly different depending on your web server, see below for some examples.
NOTE: SecRequestBodyNoFilesLimit changes the max size for the request body, and not the max file upload size. Due to how Nextcloud iOS uploads files ModSecurity does not recognize it as a file upload.
Apache with ModSecurity2:
<LocationMatch "(?:/index\.php/apps/files/ajax/upload\.php|/remote\.php/dav/(?:bulk|files/|uploads/))">
SecRequestBodyLimit 10737418240
SecRequestBodyNoFilesLimit 10737418240
</LocationMatch>
nginx with libModSecurity3:
location ~ (?:/index\.php/apps/files/ajax/upload\.php|/remote\.php/dav/(?:bulk|files/|uploads/)) {
modsecurity_rules 'SecRequestBodyLimit 10737418240
SecRequestBodyNoFilesLimit 10737418240';
}
Apache with libmodsecurity3:
<LocationMatch "(?:/index\.php/apps/files/ajax/upload\.php|/remote\.php/dav/(?:bulk|files/|uploads/))">
modsecurity_rules 'SecRequestBodyLimit 10737418240
SecRequestBodyNoFilesLimit 10737418240';
</LocationMatch>
The Nextcloud iOS app does not set the correct content type when uploading files, which causes issues with ModSecurity as it relies on the content type to correctly parse data.
There's a workaround included with the plugin but it's disabled by default due to a bypass risk, if you use the Nextcloud iOS app then uncomment rule 9508011
in nextcloud-rule-exclusions-config.conf
to enable the workaround.
The workaround will be removed when this issue is fixed within the iOS app.
See: nextcloud/ios#1942
The Nextcloud Server Crawler is used by Nextcloud for various functions of Nextcloud such as generating document previews with Collabora, and testing the functionality of Nextcloud (for example, when setting up the high performance backend for files).
Copy this rule and replace your-server-ip
with your Nextcloud Server's IP address.
Your Nextcloud Server's IP address will either be your server's WAN IP, or if your server is behind a NAT firewall then it's either your server's private IP address or your default gateway's IP address (Depending on your NAT configuration).
# Allow Nextcloud Server Crawler to crawl Nextcloud
# Generating document previews with Collabora
# Sometimes the server crawler's user agent will be missing/empty or an accept header is missing
SecRule REMOTE_ADDR "@ipMatch your-server-ip" \
"id:9508032,\
phase:1,\
pass,\
t:none,\
nolog,\
ctl:ruleRemoveById=920300,\
ctl:ruleRemoveById=920320,\
ctl:ruleRemoveById=920330,\
ctl:ruleRemoveTargetById=920120;FILES_NAMES,\
ctl:ruleRemoveTargetById=920121;FILES_NAMES,\
ctl:ruleRemoveTargetById=922130;MULTIPART_PART_HEADERS"
After the plugin is enabled, Nextcloud should work without problems caused by CRS (for example, false positives while blocking requests). If problems still occur then please file a new issue on GitHub. (Note that high paranoia level deployments may require additional tuning beyond this plugin.)
Copyright (c) 2022-2025 OWASP CRS project. All rights reserved.
The OWASP CRS and its official plugins are distributed under Apache Software License (ASL) version 2. Please see the enclosed LICENSE file for full details.