code.vikunja.io/api is vulnerable to Authorization Bypass
72
CVE Score
High
Authorization Bypass
TaskCollection.ReadAll resolves the project view from the URL path via GetProjectViewByIDAndProject before any authorization check, and the link-share branch pins task scope to the share's own project while still using that attacker-controlled view. A holder of any project share link can therefore request another tenant's kanban view and receive that view's bucket records, including bucket titles and each bucket's full created_by user object (username, name, and id), for every view on the instance. The same pre-authorization view load also acts as a project/view-ID existence oracle via 404 versus non-404 responses. The fix pins the requested project to the link share's own project before the view is loaded so foreign views cannot be resolved.
Upgrade the code.vikunja.io/api library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and link sharing is enabled so callers can authenticate with a project share link.
0.24.0 - 2.3.0
Fixed in 2.4.0code.vikunja.io/api is vulnerable to Authorization Bypass in versions 0.24.0 - 2.3.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.