漏洞信息
尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。
Vulnerability Title
Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision
Vulnerability Description
Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability Type
授权机制不正确
Vulnerability Title
Vikunja 授权问题漏洞
Vulnerability Description
Vikunja是Vikunja团队开源的一个待办事项应用程序。 Vikunja 0.22.0版本至2.3.0版本存在授权问题漏洞,该漏洞源于API令牌管理未验证主体类型,用户ID和链接共享ID独立编号且均通过web.Auth.GetID()接口解析,当链接共享JWT的数字ID与目标用户ID相同时会被视为该用户,可能导致经过身份验证的攻击者列出、创建和删除目标用户的API令牌。
CVSS Information
N/A
Vulnerability Type
N/A