Vikunja authorization bypass in API token permission keys
go-vikunja vikunja
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go-vikunja vikunja |
|
|
Original description
Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.
From the CVE record · VulnCheck