Vikunja
Vikunja: Scoped API token can mint unrestricted OAuth session credentials
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.
Affected versions and mitigation
From the CVE record, GitHub Security Advisories and the vendor's references.Affected
- = 2.3.0
- >= 2.3.0, < 2.4.0
Fixed in 2.4.0
from GitHub Security Advisory GHSA-v3p6-34mc-hj7v
Mitigation
Upgrade code.vikunja.io/api to 2.4.0 or later.
References
- Vendor advisory github.com/go-vikunja/vikunja/security/advisor…
- Patch github.com/go-vikunja/vikunja/commit/4ae2e0930…
- Release notes github.com/go-vikunja/vikunja/releases/tag/v2.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.