CVE Vulnerability Catalog

openssl_encrypt before 1.4.9 derives the remote-pepper wrap key using unsalted HKDF-SHA256 or bare SHA-256 of the password, allowing identical keys across all users and files. Attackers with access to wrapped pepper blobs can precompute a single dictionary table and perform fleet-wide offline password guessing at hardware speed to recover user passwords.

openssl_encrypt before version 1.4.9 stores an unkeyed SHA-256 hash of the plaintext in the cleartext file header. Attackers without the password can read this hash to confirm guessed plaintexts offline or fingerprint identical plaintexts across separately-encrypted files.

openssl_encrypt (pip package openssl-encrypt) versions 1.4.8 and earlier store an mTLS client private key in cleartext within a world-readable (0644) SharedPreferences file. A local attacker with file system access can read the exposed private key. Version 1.4.9 writes the PEM to a dedicated 0600 file and scrubs existing cleartext values.

OpenRemote before version 1.28.0 contains a cross-realm information disclosure vulnerability in the Notification REST API. Tenant administrators can read all tenants' sent notifications including message bodies by submitting a zero-parameter GET request to the notification endpoint.

AVideo before version 24.0 contains a server-side request forgery vulnerability in the isSSRFSafeURL function that fails to extract embedded IPv4 addresses from NAT64, 6to4, and Teredo IPv6 transition address formats. Unauthenticated attackers can bypass SSRF protections via the LiveLinks proxy endpoint to reach internal services and cloud metadata endpoints.

Baserow dispatches an Application Builder data source without acting on the result of its permission check. The dispatch and record-name views are declared with a permission class that admits any caller, and the permission check does not halt execution. An unauthenticated request can receive rows and fields from the data source, and identifiers are small integers that can be enumerated. Version 2.3.1 passes raise_exception to the same call.

The execute_ruby tool is documented as a read-only Ruby sandbox, but its denylist does not cover the spawn entry points of the pseudo-terminal library. A normal tool call could start a shell and execute commands as the server account. Version 1.6.1 restricts allowed requires and blocks dynamic dispatch, and 2.0.0 removes the tool.

The get-html-skeleton tool fetched a URL supplied by the caller after checking only its syntax. The validation did not inspect the host name or the resolved address, so loopback, link-local and private ranges were allowed, including cloud instance metadata addresses. Any caller of the MCP server could read the result of a request to an internal endpoint. Version 0.9.12 removes the tool.

The proxy middleware in mcp-use's inspector forwards requests to a destination named by the caller without inspecting the host. Loopback, link-local and private addresses were accepted, and validation was not reapplied to redirects. A caller could make the server issue requests to addresses reachable only from the host and read the responses. The current code calls isSafeProxyTarget, which checks addresses before proxying and bounds redirects.

In the resolv gem before version 0.7.2 for Ruby, during decoding of DNS responses, a new class is generated for each unknown record (type, class) pair or SvcParamKey, and permanently registered as a constant and in hashes, causing unbounded memory growth. An attacker controlling DNS responses can send a response with thousands of unknown types, causing permanent process memory growth that is not reclaimed by GC.

APITable through 1.13.0-beta.1 annotates both getUserHistories and closePausedUserAccount with requiredLogin = false. ResourceInterceptor honors that annotation by returning before any session or API key is validated, and the nginx gateway proxies every /api request to the backend. An unauthenticated attacker can enumerate accounts in the cooling-off period and close them, deleting account data and preventing recovery.

The Twig sandbox mechanism in Craft CMS is configured to allow dangerous functionality from the Yii framework, leading to authenticated RCE similar to previously disclosed vulnerabilities.

A flaw was found in rsyslog. An unauthenticated remote attacker can trigger a heap buffer overflow in the RainerScript `replace()` function by sending specially crafted syslog messages. This vulnerability arises from an incorrect buffer size calculation during string replacement, causing memory corruption. Successful exploitation can lead to a denial of service (DoS) for the affected system.

GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect outbound model requests to an externally-controlled endpoint via a crafted inline flow configuration that overrides the HTTP Host header, resulting in disclosure of Google Cloud Vertex cloud service credentials and private signing keys.

A flaw was found in Undertow. A remote attacker could exploit this vulnerability by sending specially crafted WebSocket messages with permessage-deflate negotiated. This could lead to excessive memory consumption due to the PerMessageDeflateFunction.largerBuffer() method using exponential doubling, resulting in a Denial of Service (DoS) for the affected application.

Substance3D - Sampler versions 5.1.3 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

A vulnerability in the NssaiAvailabilitySubscriptionCreate component of free5gc v4.0.1 allows an attacker to cause a Denial of Service (DoS) via a crafted POST request.

A NULL pointer dereference in the CDR processing path of free5gc v4.0.1 allows attackers to cause a Denial of Service (DoS) by supplying a crafted payload.

An issue in the RechargePut function of free5gc v4.0.1 allows attackers to cause a Denial of Service (DoS) via crafted input.

An issue in the HandleGetSharedData function of free5gc v4.0.1 allows attackers to cause a Denial of Service (DoS) via crafted input.