CVE Vulnerability Catalog

A vulnerability in Temporal Server allows a connected peer cluster to modify local namespaces in the receiving cluster, which should not be replicated. The receiving cluster does not check if the namespace is global and overwrites its state, description, owner, retention, archival settings, cluster list, and active cluster if the task carries a higher failover version. An attacker controlling a registered peer's replies can change any local namespace without credentials on the receiving cluster, e.g., marking it Deprecated, causing new Workflow starts to fail.

A vulnerability in obsidian-tc, a Model Context Protocol server for Obsidian vaults, before version 1.3.1, does not validate Host or Origin headers or enable DNS-rebinding protection in the Streamable HTTP transport. With loopback configuration using auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and gain unrestricted vault access via the http-local caller. Version 1.3.1 fixes the issue by enabling host, origin, and DNS-rebinding validation.

A vulnerability in Edimax BR-6208AC router version 1.32 affects unknown code in the file /goform/formAccept. Manipulating the submit-url argument results in command injection. The attack can be carried out remotely, and the exploit has been made public. The vendor was contacted but did not respond, and the product is no longer supported.

A Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress plugin (patreon-connect) up to version 1.10.0. It allows an attacker to force an authenticated user to perform unwanted actions in the context of their session.

A Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress plugin (patreon-connect) up to version 1.9.17. It allows an attacker to force an authenticated user to perform unwanted actions in the context of their session.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 may use cleartext transport for Amazon S3 connections by default. A network-positioned attacker could intercept data or credentials transmitted through an affected connection.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not consistently validate TLS certificate hostnames for certain outbound connections. A network-positioned attacker could exploit this weakness to intercept or modify communications with an affected service.

Progress MarkLogic Server 12.x releases before 12.1.0 may use cleartext transport for certain cluster-management communications. A network-positioned attacker could intercept or modify information transmitted through an affected connection.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not sufficiently verify the identity of a Kerberos authentication service in certain password-based authentication configurations. A network-positioned attacker could impersonate trusted authentication infrastructure, potentially resulting in unauthorized access or modification of protected data.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 assign overly permissive operating-system permissions to certain log files, which could allow a local user to read or alter log data. The corrected default permissions apply to newly created and rotated logs; existing logs retain their current permissions until remediated.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 enable XML external entity processing by default in multiple server paths, which could allow crafted XML to cause server-side requests or disclosure of local files.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain an out-of-bounds write vulnerability in certain language-processing functionality. A remote authenticated attacker could exploit this vulnerability to cause server instability or limited modification of data.

Progress MarkLogic Server 12.x releases before 12.1.0 contain an out-of-bounds read vulnerability in certain query-processing functionality. A remote authenticated attacker could exploit this vulnerability to cause server instability or disclose limited information from process memory.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not sufficiently restrict access to certain security-sensitive information. A remote authenticated attacker with limited management permissions could obtain this information, which could result in unauthorized access to protected resources.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain memory-safety defects in the JavaScript engine integration that could result in memory corruption, controlled process failure, or server instability.

A vulnerability in Progress MarkLogic Server before versions 12.1.0 and 11.3.7 allows an authenticated Query Console user to supply unsafe path values to a privileged filesystem helper, potentially resulting in disclosure of arbitrary server files.

Progress MarkLogic Server before versions 12.1.0 and 11.3.7 includes deprecated OpsDirector functionality with weaknesses that could allow an unauthenticated remote attacker to make unauthorized requests to internal services or forge trusted requests, potentially resulting in unauthorized access to protected information.

Progress MarkLogic Server before versions 12.1.0 and 11.3.7 contains an improper authentication vulnerability in SAML processing. In deployments using SAML authentication, an unauthenticated remote attacker could cause the server to accept an assertion that should be rejected, potentially resulting in unauthorized access.

On Azure deployments, Progress MarkLogic Server before versions 12.1.0 and 11.3.7 may record security-sensitive authentication information in diagnostic logs under certain configurations. An attacker with access to the affected logs could use this information to obtain unauthorized access to protected cloud resources.

Progress MarkLogic Server before versions 12.1.0 and 11.3.7 use predictable CSRF tokens in Query Console. A remote attacker who lures an authenticated Query Console user to a malicious page could submit unauthorized requests and execute server-side code with the victim's permissions.