Bug 2018282 (CVE-2021-41177) - CVE-2021-41177 nextcloud: rate-limits not working on instances without configured memory cache backend
Summary: CVE-2021-41177 nextcloud: rate-limits not working on instances without config...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-41177
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2018283
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-28 17:52 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-10-28 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-28 20:07:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-10-28 17:52:03 UTC
Nextcloud is an open-source, self-hosted productivity platform. Prior to versions 20.0.13, 21.0.5, and 22.2.0, Nextcloud Server did not implement a database backend for rate-limiting purposes. Any component of Nextcloud using rate-limits (as as `AnonRateThrottle` or `UserRateThrottle`) was thus not rate limited on instances not having a memory cache backend configured. In the case of a default installation, this would notably include the rate-limits on the two factor codes. It is recommended that the Nextcloud Server be upgraded to 20.0.13, 21.0.5, or 22.2.0. As a workaround, enable a memory cache backend in `config.php`.

Reference:
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-fj39-4qx4-m3f2

Comment 1 Guilherme de Almeida Suckevicz 2021-10-28 17:52:17 UTC
Created nextcloud tracking bugs for this issue:

Affects: fedora-all [bug 2018283]

Comment 2 Product Security DevOps Team 2021-10-28 20:07:51 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.