CVE-2021-43820
This vulnerability makes it possible to use any valid sync token to access data from any **known** library.
Does this matter?
Lower severity and a low EPSS score (0.96%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.9 MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.96% probability · 60th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-639
- Affected
- seafile/seafile server
- Source
- security-advisories@github.com
References
- https://github.com/haiwen/seafile-server/pull/520Patch, Third Party Advisory
- https://github.com/haiwen/seafile-server/security/advisories/GHSA-m3wc-jv6r-hvv8Third Party Advisory
- https://github.com/haiwen/seafile-server/pull/520Patch, Third Party Advisory
- https://github.com/haiwen/seafile-server/security/advisories/GHSA-m3wc-jv6r-hvv8Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.