Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.5%
exploitation probability
0.5%top 63% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
go-vikunja · vikunjaReferences
https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1bhttps://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0ehttps://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4https://vikunja.io/changelog/vikunja-v2.2.2-was-released