{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41177 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-41177 is a high-severity vulnerability in Nextcloud Nextcloud Server, published on 25 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41177 and fix it if it is affected.\n\nWhat it is: CVE-2021-41177 is a high-severity vulnerability in Nextcloud Nextcloud Server, published on 25 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41177 in the wild and no public exploit code.\n\nAffected product: Nextcloud Nextcloud Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-41177/ (Markdown: https://insights.sbomify.com/CVE-2021-41177/index.md)","id":"CVE-2021-41177","markdown":"https://insights.sbomify.com/CVE-2021-41177/index.md","name":"CVE-2021-41177","record":{"aliases":["GHSA-fj39-4qx4-m3f2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Nextcloud Server","requires_auth":"low_privilege","summary":"Attackers can bypass rate limits on two-factor authentication codes in Nextcloud instances lacking a configured memory cache backend.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nextcloud_server","vendor":"nextcloud"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"}],"description":"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Rate-limits not working on instances without configured memory cache backend","id":"CVE-2021-41177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nextcloud:nextcloud_server","products":["nextcloud:nextcloud_server"],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"File Traversal affecting SVG files on Nextcloud Server","id":"CVE-2021-41178"},"packages":[],"prev":{"headline":"logout CSRF in Pterodactyl Panel","id":"CVE-2021-41176"},"products":["security-advisories"],"published":"2021-10-25","related":[{"cvss_score":9.3,"headline":"Preview generation used third-party library not suited for user-generated content in Nextcloud server","id":"CVE-2021-32802","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":9.1,"headline":"Scope of workflow operations is not validated in nextcloud server","id":"CVE-2023-26482","kev_date_added":null,"published":"2023-03-30"},{"cvss_score":8.8,"headline":"Auth bypass in Nextcloud Server","id":"CVE-2018-3775","kev_date_added":null,"published":"2018-08-12"},{"cvss_score":8.7,"headline":"Nextcloud Server password reset endpoint is not brute force protected","id":"CVE-2023-35172","kev_date_added":null,"published":"2023-06-23"},{"cvss_score":8.7,"headline":"Nextcloud Server's brute force protection allows someone to send more requests than intended","id":"CVE-2023-32320","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.6,"headline":"Trusted servers exchange can be triggered by attacker","id":"CVE-2021-32656","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.5,"headline":"Nextcloud Server users can make external storage mount points inaccessible for other users","id":"CVE-2023-48239","kev_date_added":null,"published":"2023-11-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["nextcloud"]},"summary":"Attackers can bypass rate limits on two-factor authentication codes in Nextcloud instances lacking a configured memory cache backend.","url":"https://insights.sbomify.com/CVE-2021-41177/"}