grist-core has insufficient access control in endpoints for comparisons between documents and versions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gristlabs | grist-core | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Getgrist | Grist-core | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.241% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:getgrist:grist-core:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Getgrist
Getgrist grist-core |
|
| Vendors & Products |
Getgrist
Getgrist grist-core |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | grist-core is a spreadsheet hosting server. Prior to version 1.7.7, a user with only partial read access to a document could still access endpoints listing hashes for versions of that document and receive a full list of changes between versions, even if those changes contained cells, columns, or tables to which the user was not supposed to have read access. This was fixed in version 1.7.7 by restricting the `/compare` endpoint to users with full read access. As a workaround, remove sensitive document history using the `/states/remove` endpoint. Another possibility is to block the `/compare` endpoint. | |
| Title | grist-core has insufficient access control in endpoints for comparisons between documents and versions | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|