Vikunja is an open-source self-hosted task management platform. Starting in version 0.18.0 and prior to version 2.2.1, when a user account is disabled or locked, the status check is only enforced on the local login and JWT token refresh paths. Three other authentication paths — API tokens, CalDAV basic auth, and OpenID Connect — do not verify user status, allowing disabled or locked users to continue accessing the API and syncing data.
Version 2.2.1 patches the issue.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Vikunja Vikunja
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
|
0.18.0
|
2.2.1
|
References 6
https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339…
security-advisories@github.com
https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe1…
security-advisories@github.com
https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc6…
security-advisories@github.com
https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818…
security-advisories@github.com
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4
security-advisories@github.com
https://vikunja.io/changelog/vikunja-v2.2.2-was-released
security-advisories@github.com