{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43820 is a high-severity missing authorization vulnerability in haiwen seafile-server, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43820 and fix it if it is affected.\n\nWhat it is: CVE-2021-43820 is a high-severity missing authorization vulnerability in haiwen seafile-server, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43820 in the wild and no public exploit code.\n\nAffected product: haiwen seafile-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-43820/ (Markdown: https://insights.sbomify.com/CVE-2021-43820/index.md)","id":"CVE-2021-43820","markdown":"https://insights.sbomify.com/CVE-2021-43820/index.md","name":"CVE-2021-43820","record":{"aliases":["GHSA-m3wc-jv6r-hvv8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Seafile cloud storage","requires_auth":"none","summary":"Attackers with a valid sync token can access data from any known library by bypassing library-specific authorization checks in Seafile server.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"seafile_server","vendor":"seafile"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Seafile is an open source cloud storage system. A sync token is used in Seafile file syncing protocol to authorize access to library data. To improve performance, the token is cached in memory in seaf-server. Upon receiving a token from sync client or SeaDrive client, the server checks whether the token exist in the cache. However, if the token exists in cache, the server doesn't check whether it's associated with the specific library in the URL. This vulnerability makes it possible to use any valid sync token to access data from any **known** library. Note that the attacker has to first find out the ID of a library which it has no access to. The library ID is a random UUID, which is not possible to be guessed. There are no workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Permissions check bypass in Seafile","id":"CVE-2021-43820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Files Accessible to External Parties in Opencast","id":"CVE-2021-43821"},"packages":[],"prev":{"headline":"Stargate-Bukkit improperly handles vehicles causing data duplication.","id":"CVE-2021-43819"},"products":["seafile-server"],"published":"2021-12-14","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2014-5443","kev_date_added":null,"published":"2018-03-19"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-65516","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":5.4,"headline":"Seafile Server has multiple stored XSS vulnerabilities","id":"CVE-2026-30587","kev_date_added":null,"published":"2026-03-25"}],"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":["haiwen"]},"summary":"Attackers with a valid sync token can access data from any known library by bypassing library-specific authorization checks in Seafile server.","url":"https://insights.sbomify.com/CVE-2021-43820/"}