CVE Vulnerability Catalog

A flaw was found in sblim-cmpi-base. Insecure temporary file creation in the provider registration scripts allows a local unprivileged user to perform a symlink attack. By creating a symlink in a world-writable directory, an attacker can redirect privileged writes to an arbitrary file during script execution in a privileged context. This can lead to the overwrite of root-owned files, potentially disrupting system services or operation. Exploitation is conditional on the script running with elevated privileges and may be mitigated by sticky-directory symlink protections.

A race condition flaw was found in sblim-sfcb during privileged instance migration. A local low-privileged attacker can manipulate a temporary file in /tmp by repeatedly recreating a symbolic link, redirecting privileged output to an arbitrary file. This can lead to privileged file corruption or denial of service.

An unsafe deserialization vulnerability was found in sblim-sfcb's provider-manager IPC message parsing. A local attacker can send a crafted message causing out-of-bounds memory access, leading to termination of the provider-manager process and denial of service. This could also potentially result in limited unintended information disclosure.

In PostgreSQL, missing authorization in DDL commands allows an object creator to cause denial of service against ALTER and DROP of a type by creating a dependency on it. Affected versions are before 18.6, 17.11, 16.15, 15.19, and 14.24.

In PostgreSQL, the ascii() SQL function has a buffer over-read that allows a user to disclose up to 3 bytes after the end of a specific allocation via a crafted text value. Affected versions are before 18.6, 17.11, 16.15, 15.19, and 14.24.

In PostgreSQL, improper enforcement of message integrity in GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules via initial direct TLS connection. Despite pg_hba.conf appearing to require GSSAPI, the connection may exchange data over TLS encryption alone. If TLS settings are more permissive than GSS settings, the connection may continue with lesser protection. Affected are major versions 17-18, before 18.6 and 17.11.

In PostgreSQL, the pg_trgm index picksplit function reads past the end of a heap buffer. This might allow a table maintainer to infer limited memory values via the lossy signal of index split choices. Affected versions are before 18.6, 17.11, 16.15, 15.19, and 14.24.

In PostgreSQL SCRAM authentication, an observable response discrepancy allows an unauthenticated user to test the existence of a user by observing the SCRAM iteration count. Affected are major versions 16-18, before 18.6, 17.11, and 16.15.

In PostgreSQL, incomplete tracking of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies persist until cache invalidation or session end. Affected versions are before 18.6, 17.11, 16.15, 15.19, and 14.24.

In PostgreSQL, the pgcrypto extension stores cleartext when ciphers are disabled, allowing a user to recover cleartext via direct observation of faulty ciphertext. The OpenSSL version and configuration determine disabled ciphers. If the application accepts encrypted data as input, decryption may succeed even with the wrong key, losing MDC protection. Affected versions are before 18.6, 17.11, 16.15, 15.19, and 14.24.

HCL AION is affected by a vulnerability where the shared storage used by product components is architected without sufficient access separation. Processes sharing the storage may be able to access or modify files beyond their intended scope, potentially resulting in unintended behavior or security impact under certain conditions.

Serendipity versions >= 2.3.5 and <= 2.6.0 contain a reflected cross-site scripting vulnerability in the search clean-URL route (/search/<term>). In include/functions_routing.inc.php serveSearch(), the sanitisation pipeline runs urldecode() after HTML-encoding, so a single URL-encoded HTML payload survives strip_tags() and htmlspecialchars() and is then decoded back into live HTML in the page. A crafted search link can execute arbitrary JavaScript in the victim's browser. Fixed in 2.6.1.

JupyterLab (pip package 'jupyterlab') versions >=4.1.0,<=4.5.9 and >=4.6.0,<=4.6.1 contain a plugin manager lock-rule enforcement bypass. Two server-side enforcement gaps allow an authenticated user to circumvent administrator lock rules by making direct requests to the /lab/api/plugins endpoint, enabling or disabling plugins that were locked — including child plugins of multi-plugin extensions and plugins locked via the 'lock all' mechanism. This can impact data integrity and bypass hardening or restrictions (e.g., download/upload limits) implemented through locked plugins. Fixed in versions 4.6.2 and 4.5.10.

GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).

GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.

OpenRemote notification deletion endpoints fail to enforce realm boundaries, allowing any realm administrator to delete notifications belonging to other realms. Attackers with write:admin role in one realm can send DELETE requests to remove notifications from the master realm or other tenants without authorization checks.

File Browser versions from 2.50.0 through 2.63.21 fail to validate JWT expiration when proxy authentication is configured with a non-default logout page. Attackers with a previously valid token can access protected routes and administrative endpoints indefinitely, and exchange expired tokens for fresh ones via the renewal endpoint.

SiYuan before v3.7.4 contains an information disclosure vulnerability in the local storage filter that returns the administrator's entire storage map with only three keys sanitized. Unauthenticated attackers or publish readers can retrieve closed-tab history, search keywords, private document identifiers, and expanded folder paths by calling the getLocalStorage endpoint.

SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the getBookmarkLabels endpoint that returns all bookmark labels in the workspace without publish-access filtering. Anonymous readers and publish-mode readers can obtain the complete bookmark vocabulary across the workspace, disclosing subject matter and organizational information from inaccessible documents.

SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the /api/storage/getOutlineStorage endpoint that performs no authorization checks. Attackers can retrieve outline state including heading identifiers for any document by supplying its identifier, even for documents forbidden to the requester.