CVE-2021-41177: Rate-limits not working on instances without configured memory cache backend
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nextcloud (openSUSE:Leap 15.2) 20.0.14-bp153.2.9.1; nextcloud (SUSE:Package Hub 12) 20.0.14-bp153.2.9.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to nextcloud (openSUSE:Leap 15.2) 20.0.14-bp153.2.9.1; nextcloud (SUSE:Package Hub 12) 20.0.14-bp153.2.9.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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`.
- Published
- Oct 25, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.5% · 75th percentile
- CWE
- CWE-799
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
CNA vs NVD score
- NVD
- 8.1
- CNA · GitHub_M
- 8.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nextcloud | nextcloud server | cpe:2.3:a:nextcloud:nextcloud_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
nextcloud security-advisories
- < 20.0.13, >= 21.0.0, < 21.0.5, < 22.2.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nextcloud nextcloud serverbefore 20.0.13
- nextcloud nextcloud server21.0.0 and later · before 21.0.5
- nextcloud nextcloud server22.0.0 and later · before 22.2.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.2 | nextcloud | before 20.0.14-bp153.2.9.1 | 20.0.14-bp153.2.9.1 |
| SUSE:Package Hub 12 | nextcloud | before 20.0.14-bp153.2.9.1 | 20.0.14-bp153.2.9.1 |
Same product
nextcloud: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-26482Scope of workflow operations is not validated in nextcloud server40Plan
- CVE-2021-32802Preview generation used third-party library not suited for user-generated content in Nextcloud server40Plan
- CVE-2021-32726Webauthn tokens not removed after user has been deleted40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-32800Sep 7, 2021 · Bypass of Two Factor Authentication in Nextcloud server33Monitor
- ← EarlierCVE-2021-32801Sep 7, 2021 · Exceptions may have logged Encryption-at-Rest key content in Nextcloud server22Monitor
- Later →CVE-2021-41239Mar 8, 2022 · User enumeration setting not respected in Nextcloud server21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:nextcloud | 20.0.14-bp153.2.9.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:nextcloud | 20.0.14-bp153.2.9.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0869 · Oct 26, 2021(Nextcloud Zafiyeti)
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-799 · Improper Control of Interaction FrequencyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.