Vikunja: Scoped API token can mint unrestricted OAuth session credentials

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

Vikunja is an open-source self-hosted task management platform. In version 2.3.0, a scoped API token limited to the `oauth.authorize` permission can call `POST /api/v1/oauth/authorize`, obtain an OAuth authorization code, and exchange the code at `POST /api/v1/oauth/token` for a normal bearer JSON Web Token (JWT) and refresh token. The resulting credentials are not restricted by the original API token's permissions, allowing access to routes outside its declared scope for the same user. Version 2.4.0 fixes the vulnerability.

[ Fixes ]Fixes and patches

• code.vikunja.io/api 2.4.0Fixed version · GitHub Advisories · go package code.vikunja.io/api: upgrade to 2.4.0 or later (affected = 2.3.0)

[ Packages ]Affected open-source packages

• code.vikunja.io/api goAffected = 2.3.0 · fixed in 2.4.0 · GHSA-v3p6-34mc-hj7v

[ References ]References

• github.com/go-vikunja/vikunja/commit/4ae2e093014881052ed8f8ecd8bcb9adf83dd276
• github.com/go-vikunja/vikunja/releases/tag/v2.4.0
• github.com/go-vikunja/vikunja/security/advisories/GHSA-v3p6-34mc-hj7v