Two-factor code brute-force via skipped rate limiting
Published Oct 25, 2021 · Updated Aug 4, 2024
Improper rate limiting in Nextcloud Server before 20.0.13, 21.0.5, and 22.2.0 allows remote authenticated users to brute-force two-factor codes. When no distributed memory cache is configured, the rate-limit check is skipped instead of falling back to persistent storage. A default installation leaves two-factor-code attempts unthrottled, allowing repeated guesses but not directly granting access without a valid code.
Summary
What happened
Improper rate limiting in Nextcloud Server before 20.0.13, 21.0.5, and 22.2.0 allows remote authenticated users to brute-force two-factor codes. When no distributed memory cache is configured, the rate-limit check is skipped instead of falling back to persistent storage. A default installation leaves two-factor-code attempts unthrottled, allowing repeated guesses but not directly granting access without a valid code.
The record
- CVE
- CVE-2021-41177
- Published
- Oct 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Nextcloud GmbH
- Product
- Nextcloud Security Advisories
- Classifications
- CWE-799, T1110
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 20.0.13
- Affected versionversion=>= 21.0.0, < 21.0.5
- Affected versionversion=< 22.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo