| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Vikunja from 2.4.0 before 2.8.0 contains a denial of service vulnerability in the richtext converter that allows authenticated project writers to exhaust server memory and CPU by storing tables with unbounded rowspan and colspan values. Any project reader or CalDAV client can trigger the expansion through markdown task reads, CalDAV GETs, or the frontend editor, producing 100 MB responses from a 64-byte description. |
| Vikunja from 0.19.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated users to exhaust CPU by supplying unbounded business-day operands in datemath filters. Attackers can send task or time-tracking filters like due_date > now+999999999999b, triggering a per-day loop in go-datemath that pins CPU cores and exhausts the server. |
| Vikunja from 0.21.0 before 2.8.0 contains a resource exhaustion vulnerability that allows authenticated users to trigger instance-wide database writes by setting a project position below 0.1. Attackers can repeatedly send PUT requests to /api/v2/projects/{id} so recalculateProjectPositions updates every user's root projects, holding SQLite's write lock and degrading availability. |
| Vikunja from 0.18.0 before 2.8.0 contains a resource amplification vulnerability in pkg/models/export.go that allows authenticated users to exhaust server memory by exporting heavily related tasks. Attackers can relate many tasks to one task with a large description and request a user export, causing an out-of-memory crash for all users. |
| Vikunja from 1.0.0 before 2.8.0 contains a memory exhaustion vulnerability that allows authenticated users to crash the server by uploading extreme-width images as task attachments. Attackers can request the attachment preview endpoint so Lanczos resampling allocates width-proportional weight tables, OOM-killing the process repeatedly with sub-megabyte PNGs. |
| Vikunja from 0.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators' email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members. |
| Vikunja from 2.6.0 before 2.8.0 contains a resource exhaustion vulnerability in the Planka migration converter that multiplies task allocations for duplicate list IDs. Attackers controlling a Planka server can return boards with duplicate list IDs and many cards to exhaust memory and OOM-kill the Vikunja process. |
| Vikunja from 0.8.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated project readers to amplify response size by repeating requested properties in CalDAV PROPFIND requests. Attackers can send PROPFIND requests to the dav projects endpoint with hundreds of duplicate calendar-data properties to exhaust server memory, CPU, and bandwidth. |
| Vikunja from 2.2.1 before 2.8.0 contains a TOTP replay protection bypass in ValidateTOTPPasscode that allows attackers to reuse consumed codes by padding them with whitespace. Attackers with valid credentials who observe a used passcode can resubmit it whitespace-padded to the login API within the validity window to obtain a session token. |
| Vikunja from 0.16.0 before 2.8.0 contains an information disclosure vulnerability that writes users' Trello API tokens to application logs and Sentry by formatting provider errors verbatim in listeners.go. When a Trello migration fails with a transport error, the URL error embeds the token query parameter, letting anyone with log or telemetry access obtain the reusable third-party credential. |
| Vikunja from 0.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log victims into the attacker's account and view the victims' entered data. |
| Vikunja 0.17.0 before 2.8.0 builds the task.deleted notification and webhook payload, including related tasks, with the deleting user's permissions and sends it to all project subscribers without per-recipient authorization checks. A user subscribed to a project, or owning its webhook, receives full data of related tasks in private projects they cannot read when a task in their project is deleted. |
| Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to read other users' private projects through the tasks.overdue webhook payload. Attackers can register a personal tasks.overdue webhook with one subscribed overdue task, then receive project titles, descriptions, and owner IDs from other users' reminders at external URLs. |
| Vikunja from 0.14.0 before 2.8.0 contains a mass assignment vulnerability that allows authenticated users to set json-hidden fields by sending XML request bodies to the v1 API. Attackers can set BackgroundFileID on project creation to download any stored file via the background endpoint, or create bots with IsAdmin set to gain instance-admin access. |
| Vikunja from 1.0.0 before 2.8.0 contains an account takeover vulnerability that allows attackers to hijack SSO identities by planting local accounts with unverified victim emails. When emailfallback is enabled, attackers register or edit a local account using the victim's email, causing the victim's first OIDC login to link into the attacker-controlled account and expose their data. |
| SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows clients with table write access to persist writes refused by THROWing table events within interactive transactions. Attackers can run a guarded statement via RPC begin and query, ignore the returned error, and commit to persist the record and event side effects. |
| SurrealDB 1.0.0 before 4.0.0 prints SURREAL_PASS and SURREAL_TOKEN environment variable values in clear text in the --help and -h output of CLI commands such as surreal start, sql, import, export, and mcp, because the arguments do not set clap's hide_env_values. Anyone who later sees that terminal output, for example in shell logs, CI logs, or screen shares, can obtain root database credentials. |
| SurrealDB 2.2.0 before 4.0.0 includes the record id of a referencing row in the error returned when a delete is blocked by an ON DELETE REJECT reference, without checking the caller's SELECT permission on that row. An authenticated principal with DELETE permission can attempt to delete a referenced record and read the rejection error to learn the existence and exact ids of referencing records hidden by row-level SELECT permissions. |
| SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in its filesystem storage bucket that only canonicalizes the bucket root, not descendant symlinks. Attackers can reference paths through a pre-existing symlink inside the bucket that pass the lexical prefix check, reading and writing files across the host filesystem. |
| SurrealDB 1.0.0 before 4.0.0 contains a capability check bypass in its embedded JavaScript scripting engine, where the surrealdb.functions bridge calls the internal fnc::synchronous() and fnc::asynchronous() dispatchers without enforcing function capability checks. Authenticated users denied access to built-in functions in SurrealQL can execute them by calling them through surrealdb.functions from embedded JavaScript. |