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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| go-vikunja | vikunja | 2.4.0 – < 2.7.1 | 2.7.1 |
References
- GitHub Security Advisory (GHSA-j5v7-qcwp-5g32) vendor-advisory
- VulnCheck Advisory: Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass third-party-advisory