SurrealDB versions prior to 4.0.0 have an authorization vulnerability in the filter_fields_by_permission function. This flaw allows authenticated users to read child field values that should be denied by SELECT permissions due to incorrect handling of permission checks on nested array elements.
SurrealDB versions prior to 4.0.0 have a guard bypass vulnerability that permits authenticated users to execute write subqueries within LIVE query WHERE clauses or field projections. This flaw enables injection of CREATE, UPDATE, DELETE, or RELATE statements that execute atomically inside other users' transactions. The vulnerability can lead to amplified write operations and unauthorized exfiltration of document data even after permissions have been revoked.
SurrealKV versions before 1.1.0 have an out-of-bounds read vulnerability in the InternalKeyRef::from_encoded constructor. This constructor only performs key length checks using debug-only assertions, which are not enforced in production. If callers provide keys shorter than 16 bytes or if SSTable blocks are crafted or corrupted, this can cause unchecked length underflow in functions like timestamp(), seq_num(), and trailer(), leading to reading memory before the allocated buffer or causing a panic.
SurrealDB versions 3.0.0 up to but not including 4.0.0 contain an authorization bypass vulnerability. This flaw allows clients with table write access to persist writes that should be refused by exploiting THROWing table events within interactive transactions. Attackers can execute guarded statements via RPC begin and query, ignore errors, and commit changes to persist unauthorized records and side effects.
Vikunja versions from 0.8.0 up to but not including 2.8.0 contain a denial of service vulnerability. Authenticated project readers can exploit this by sending CalDAV PROPFIND requests with repeated properties, causing excessive resource consumption on the server. This leads to exhaustion of memory, CPU, and bandwidth, resulting in denial of service.
Vikunja versions from 2.2.0 up to but not including 2.8.0 have an information disclosure vulnerability. Authenticated users can exploit the tasks.overdue webhook to read private project details of other users, including project titles, descriptions, and owner IDs. This occurs by registering a personal tasks.overdue webhook with a subscribed overdue task and receiving sensitive data at external URLs.
OpenRemote core versions before 1.34.0 have an authentication bypass vulnerability in the UserAssetProvisioningMQTTHandler component. This flaw allows unauthenticated attackers to impersonate provisioned devices by publishing a known device's public certificate to the provisioning request topic. As a result, attackers can authenticate their anonymous MQTT connection as the device's service account, enabling them to read and modify assets.
Vikunja versions from 0.20.5 up to but not including 2.8.0 contain a login cross-site request forgery (CSRF) vulnerability in the OpenID Connect callback handler. This flaw allows attackers to craft a callback link with an empty state parameter and their own authorization code, causing victims to be silently logged into the attacker's account and potentially exposing their entered data.
Vikunja versions from 2.3.0 up to but not including 2.8.0 contain a vulnerability in the CSV migration module where uncontrolled memory allocation can occur. This happens because the module does not de-duplicate label column mappings or limit the number of labels per row before building the full import. Authenticated users can exploit this by sending a specially crafted request to the migration endpoint, causing the server to exhaust memory and potentially crash due to out-of-memory conditions.
Vikunja versions from 2.6.0 up to but not including 2.8.0 contain a resource exhaustion vulnerability in the Planka migration converter. This flaw allows an attacker controlling a Planka server to supply boards with duplicate list IDs and many cards, causing Vikunja to multiply task allocations excessively. The resulting memory exhaustion can lead to the Vikunja process being terminated by the operating system (OOM-killed).
Vikunja versions from 0.16.0 up to but not including 2.8.0 have an information disclosure vulnerability. This flaw causes users' Trello API tokens to be written verbatim to application logs and Sentry error telemetry when Trello migration fails due to transport errors. The token is embedded in the URL error, exposing reusable third-party credentials to anyone with access to logs or telemetry data.
OpenRemote versions from 1.2.0 up to but not including 1.34.0 have an authorization bypass vulnerability in the AlarmFacade component. This flaw allows users with write:rules permission to create alarms for assets outside their authorized ruleset subtree. Exploiting this, attackers can deploy JSON asset-scoped rulesets with custom asset IDs to generate high severity alarms and trigger operator notifications for arbitrary assets within the realm.
Vikunja versions from 0.17.0 up to but not including 2.8.0 have a vulnerability where the task.deleted notification and webhook payload include related tasks with the deleting user's permissions. This payload is sent to all project subscribers without checking authorization per recipient, potentially exposing private task data to unauthorized users subscribed to the project or owning its webhook.
Vikunja versions from 1.0.0 up to but not including 2.8.0 contain an account takeover vulnerability related to SSO identity hijacking. This occurs when the email fallback feature is enabled, allowing attackers to register or modify local accounts with unverified victim emails. As a result, the victim's first OpenID Connect (OIDC) login links to the attacker-controlled account, exposing the victim's data.
Vikunja versions from 2.2.1 up to but not including 2.8.0 have a vulnerability in the TOTP validation process. The flaw allows attackers with valid credentials to bypass replay protection by padding previously used TOTP codes with whitespace and resubmitting them within the code's validity window to gain a session token.
Vikunja versions from 0.14.0 up to but not including 2.8.0 have a mass assignment vulnerability. Authenticated users can exploit this by sending XML request bodies to the v1 API to set fields that are normally hidden in JSON. This allows attackers to set the BackgroundFileID during project creation to download any stored file or create bots with administrative privileges by setting IsAdmin, potentially gaining instance-admin access.
Vikunja versions from 1.0.0 up to but not including 2.8.0 have a memory exhaustion vulnerability. Authenticated users can exploit this by uploading extremely wide images as task attachments, causing the server to crash due to out-of-memory conditions during image preview processing.
Vikunja versions from 0.9.0 up to but not including 2.8.0 have an information disclosure vulnerability that allows project administrators to view email addresses of share creators. This occurs via the project shares endpoint, where the shared_by email field is accessible. The vulnerability exposes email addresses of creators, including those of former project members, to attackers with admin permissions.
Admidio versions prior to 5.0.18 have an insecure direct object reference (IDOR) vulnerability in the mylist.php script. This flaw allows authenticated users with access to the Lists module to read certain list configuration details of other users if they know the list's UUID. The vulnerability arises because the application verifies only the organization ownership but not the list owner or its privacy settings when loading list configurations.
Admidio versions 5.0.0 up to but not including 5.0.18 contain a path traversal vulnerability in the Documents & Files renameFile() function. Authenticated users with folder upload rights can exploit this flaw by using ../ sequences in the adm_new_name parameter to move files outside the intended directory. This allows attackers to relocate an uploaded SVG file containing malicious script to the web root, enabling stored cross-site scripting (XSS) attacks against administrators, potentially leading to account takeover.