Vikunja
Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api
Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.24.6, < 2.4.0
Fixed in 2.4.0
Mitigation
Upgrade vikunja to 2.4.0 or later.
References
- Vendor advisory github.com/go-vikunja/vikunja/security/advisor…
- Patch github.com/go-vikunja/vikunja/pull/3239
- Patch github.com/go-vikunja/vikunja/commit/6895a7765…
1 more
- Release notes github.com/go-vikunja/vikunja/releases/tag/v2.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.