4.3 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): None (N)
- Integrity (I): Low (L)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): None (N)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): Low (L)
- Modified Availability (MA): None (N)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse ignored package vikunja-desktop
- @LeSuisse accepted
- @LeSuisse published on GitHub
Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.
References
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf79-mg83 x_refsource_CONFIRM
Ignored references (2)
-
https://github.com/go-vikunja/vikunja/pull/2584 x_refsource_MISC
-
https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 x_refsource_MISC
Affected products
- ==< 2.3.0
Package maintainers
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>
-
@leona-ya Leona Maroni <nix@leona.is>