Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Nextcloud | Approval | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nextcloud | Approval |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.329% probability within 30 days)
| Link | Providers |
|---|---|
| https://hackerone.com/reports/3610332 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Approval Endpoint Bypass via Omitted ETag |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Approval Endpoint Bypass via Omitted ETag |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nextcloud
Nextcloud approval |
|
| Vendors & Products |
Nextcloud
Nextcloud approval |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Approval app's approve/reject endpoint is meant to require the file's current etag as a freshness check, preventing an approver from approving or rejecting a file whose contents changed after they reviewed it. The backend only enforced this check when the etag parameter was present and non-empty in the request. An attacker able to intercept and modify the approval request could omit the etag field entirely, bypassing the freshness check and approving or rejecting a file version they never reviewed. | |
| Weaknesses | CWE-840 | |
| References |
| |
| Metrics |
cvssV3_0
|