5.9 MEDIUM
- CVSS version: 3.1
- Attack vector (AV): NETWORK
- Attack complexity (AC): HIGH
- Privileges required (PR): NONE
- User interaction (UI): NONE
- Scope (S): UNCHANGED
- Confidentiality impact (C): HIGH
- Integrity impact (I): NONE
- Availability impact (A): NONE
Vikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/routes/api/v1/login.go calls HandleFailedTOTPAuth and then unconditionally rolls back. HandleFailedTOTPAuth in pkg/user/totp.go uses an in-memory counter (key-value store) to track failed attempts. When the counter reaches 10, it calls user.SetStatus(s, StatusAccountLocked) on the same database session s. Because the login handler always rolls back after a TOTP failure, the StatusAccountLocked write is undone. The in-memory counter correctly increments past 10, so the lockout code executes on every subsequent attempt, but the database write is rolled back every time. This allows unlimited brute-force attempts against TOTP codes. This vulnerability is fixed in 2.3.0.
References
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv97-6cmj x_refsource_CONFIRM
-
https://github.com/go-vikunja/vikunja/pull/2576 x_refsource_MISC
-
https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 x_refsource_MISC
Affected products
- ==< 2.3.0
Matching in nixpkgs
pkgs.vikunja
Todo-app to organize your life
pkgs.vikunja-desktop
Desktop App of the Vikunja to-do list app
Package maintainers
-
@leona-ya Leona Maroni <nix@leona.is>
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>