Seafile Server
Approved changes feed: RSS · Atom
cpe:2.3:a:haiwen:seafile-server:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Haiwen (59abdbb5-3b52-55bb-9ea4-6d30488a4108) |
|---|---|
| Product | Seafile Server (3ae90edc-da1d-52c4-9c95-03253ef272a0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-43820 |
vulnerable | 2026-06-08 05:36:44.371005 |
Permissions check bypass in Seafile
HIGH (7.4)
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.
Published: 2021-12-14T18:55:10.000Z
Updated: 2024-08-04T04:03:09.080Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.