Jonathan Leitschuh

**Name of the Vulnerable Software and Affected Versions** Model Context Protocol versions prior to 0.25.0 **Description** Servers fail to validate the "Origin" header on incoming connections, which may allow DNS rebinding attacks. DNS rebinding is a method of bypassing the Same-Origin Policy to interact with services on a private network from a remote browser. **Recommendations** Update to version 0.25.0 or later and use the `--allowed-hosts` or `--allowed-origins` flags to specify permitted hosts and origins at server startup.

**Name of the Vulnerable Software and Affected Versions** Microsoft Playwright MCP Server versions prior to 0.0.40 **Description** The software does not properly validate the Origin header on incoming connections. This allows an attacker to perform a DNS rebinding attack via a victim’s web browser and send unauthorized requests to a locally running MCP server. This can lead to unintended invocation of MCP tool endpoints. **Recommendations** Update to version 0.0.40 or later.

**Name of the Vulnerable Software and Affected Versions** Anyscale Ray version 2.52.0 **Description** Anyscale Ray 2.52.0 has a default configuration where token-based authentication for Ray management interfaces, including the dashboard and Jobs API, is disabled unless explicitly enabled by setting the `RAY AUTH MODE` variable to 'token'. Without authentication enabled, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. The API endpoint for job submission is vulnerable. **Recommendations** Enable token authentication by setting the `RAY AUTH MODE` variable to 'token' to protect the cluster from unauthorized access.

**Name of the Vulnerable Software and Affected Versions** cors-anywhere (affected versions not specified) **Description** Instances of cors-anywhere configured as an open proxy permit unauthenticated external users to initiate HTTP requests to arbitrary targets, leading to Server-Side Request Forgery (SSRF). The proxy forwards requests and headers, potentially granting access to internal-only endpoints and link-local metadata services. This can result in the retrieval of instance role credentials or other sensitive metadata, and interaction with internal APIs and services. Exploitation involves sending crafted requests to the proxy with the target resource encoded in the URL. Deployments that forward arbitrary methods and headers, including PUT, may allow exploitation of IMDSv2 workflows and access to internal management APIs. Successful exploitation can lead to theft of cloud credentials, unauthorized access to internal services, remote code execution, privilege escalation, data exfiltration, and full compromise of cloud resources. **Recommendations** Restrict the proxy to trusted origins or require authentication. Whitelist allowed target hosts. Prevent access to link-local and internal IP ranges. Remove support for unsafe HTTP methods and headers. Enable cloud provider mitigations. Deploy network-level protections.

**Name of the Vulnerable Software and Affected Versions** io.pebbletemplates:pebble versions (affected versions not specified) **Description** The issue allows an attacker to control file names or paths via the `include` tag, potentially accessing sensitive local files like `/etc/passwd` or `/proc/1/environ` by crafting malicious notification templates. **Recommendations** To mitigate this issue, disable the `include` macro in Pebble Templates by using the following Java code: ```java new PebbleEngine.Builder() .registerExtensionCustomizer(new DisallowExtensionCustomizerBuilder() .disallowedTokenParserTags(List.of("include")) .build()) .build(); ```

**Name of the Vulnerable Software and Affected Versions** Dependency-Track versions prior to 4.12.6 **Description** The issue allows users with the `SYSTEM CONFIGURATION` permission to abuse the `include` tag in notification templates, potentially leaking sensitive local files, such as `/etc/passwd` or `/proc/1/environ`, by including them in notification templates and sending notifications to a controlled destination. **Recommendations** For versions prior to 4.12.6, avoid assigning the `SYSTEM CONFIGURATION` permission to untrusted users, as this permission is a security risk if granted to non-administrative users or teams. Update to version 4.12.6 or later, where the `include` tag can no longer be used and its usage will cause template evaluation to fail.

**Name of the Vulnerable Software and Affected Versions** Apache Helix Front (UI) versions all **Description** The Apache Helix Front (UI) component contained a hard-coded secret, allowing an attacker to spoof sessions by generating their own fake cookies. This issue affects products that are no longer supported by the maintainer. **Recommendations** As this project is retired and no fix will be released, users are recommended to find an alternative or restrict access to the instance to trusted users.

**Name of the Vulnerable Software and Affected Versions** Apache Submarine Commons Utils versions 0.8.0 and later **Description** The issue is related to an Improper Authentication vulnerability in Apache Submarine Commons Utils. If the user doesn't explicitly set `submarine.auth.default.secret`, a default value will be used. This vulnerability only affects products that are no longer supported by the maintainer. As the project is retired, no fix will be released. **Recommendations** For Apache Submarine Commons Utils versions 0.8.0 and later, users are recommended to find an alternative or restrict access to the instance to trusted users.

**Name of the Vulnerable Software and Affected Versions** Apache Hop Engine versions prior to 2.8.0 **Description** The issue is related to improper input validation in the Apache Hop Engine, specifically affecting the Hop Server component. When the Hop Server writes links to the PrepareExecutionPipelineServlet page, one of the parameters provided to the user, the `id`, is not properly escaped. This makes the risk of exploiting this issue low, as the `id` is not directly accessible by users creating pipelines. The issue does not directly affect the client. **Recommendations** For Apache Hop Engine versions prior to 2.8.0, users are recommended to upgrade to version 2.8.0, which fixes the issue. As a temporary workaround, consider restricting access to the PrepareExecutionPipelineServlet page until the upgrade is applied. Additionally, users can minimize the risk of exploitation by being cautious when creating pipelines and avoiding any potential manipulation of the `id` variable.

**Name of the Vulnerable Software and Affected Versions** Apache Linkis versions <=1.4.0 **Description** The issue is related to insufficient protection of registration data in Apache Linkis, which may allow a remote attacker to gain unauthorized access to protected information. Specifically, when using the Oracle data source of the Linkis data source module, the password is printed to the log. **Recommendations** For Apache Linkis versions <=1.4.0, upgrade the version of Linkis to version 1.5.0 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Apache Camel versions 3.X through 3.14.8 Apache Camel versions 3.18.X through 3.18.7 Apache Camel versions 3.20.X through 3.20.5 Apache Camel versions 4.X through 4.0.0-M3 **Description** The issue is related to the exposure of sensitive information to an unauthorized actor. This vulnerability may allow an attacker to gain unauthorized access to protected information. **Recommendations** For Apache Camel versions 3.X through 3.14.8, upgrade to 3.14.9. For Apache Camel versions 3.18.X through 3.18.7, upgrade to 3.18.8. For Apache Camel versions 3.20.X through 3.20.5, upgrade to 3.20.6 or 3.21.0. For Apache Camel versions 4.X through 4.0.0-M3, update to 4.0.0-M1.

**Name of the Vulnerable Software and Affected Versions** com.fasterxml.util:java-merge-sort versions prior to 1.1.0 **Description** The issue is related to an Insecure Temporary File in the `StdTempFileProvider()` function, located in `StdTempFileProvider.java`. This function utilizes the permissive `File.createTempFile()` function, which exposes the contents of temporary files. **Recommendations** For versions prior to 1.1.0, update to version 1.1.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the `StdTempFileProvider()` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Apache James MIME4J versions prior to 0.8.9 **Description** Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users. **Recommendations** For Apache James MIME4J versions prior to 0.8.9, upgrade to MIME4j version 0.8.9 or later.

**Name of the Vulnerable Software and Affected Versions** cloudsync (affected versions not specified) **Description** A problematic vulnerability was found in cloudsync, affecting the `getItem` function of the `LocalFilesystemConnector.java` file. This vulnerability leads to path traversal and can be exploited on the local host. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Widoco (affected versions not specified) **Description** A critical vulnerability was found in Widoco, affecting the `unZipIt` function of the file `src/main/java/widoco/WidocoUtils.java`. This issue leads to path traversal and can be exploited on the local host. **Recommendations** To fix this issue, it is recommended to apply a patch with the name f2279b76827f32190adfa9bd5229b7d5a147fa92. As a temporary workaround, consider disabling the `unZipIt` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** pig-vector (affected versions not specified) **Description** A vulnerability was found in pig-vector, classified as problematic, affecting the `LogisticRegression` function of the file `src/main/java/org/apache/mahout/pig/LogisticRegression.java`. This issue leads to an insecure temporary file and requires a local attack approach. **Recommendations** To fix this issue, it is recommended to apply a patch. The name of the patch is `1e7bd9fab5401a2df18d2eabd802adcf0dcf1f15`. As a temporary workaround, consider disabling the `LogisticRegression` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** jLEMS (affected versions not specified) **Description** A critical vulnerability was found in jLEMS, affecting the `unpackJar` function of the file `src/main/java/org/lemsml/jlems/io/util/JUtil.java`. This vulnerability leads to path traversal and can be exploited remotely. **Recommendations** To fix this issue, it is recommended to apply a patch with the name 8c224637d7d561076364a9e3c2c375daeaf463dc. As a temporary workaround, consider disabling the `unpackJar` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** bspkrs MCPMappingViewer (affected versions not specified) **Description** A critical issue has been found in the `extractZip` function of the `RemoteZipHandler.java` file, part of the ZIP File Handler component. This issue leads to path traversal and can be exploited remotely. **Recommendations** To fix this issue, it is recommended to apply a patch. The name of the patch is 6e602746c96b4756c271d080dae7d22ad804a1bd. As a temporary workaround, consider disabling the `extractZip` function until a patch is available. Restrict access to the ZIP File Handler component to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** scifio (affected versions not specified) **Description** A critical vulnerability was found in scifio, affecting the function `downloadAndUnpackResource` of the file `src/test/java/io/scif/util/DefaultSampleFilesService.java` of the component ZIP File Handler. The manipulation leads to path traversal. The attack can be launched remotely. **Recommendations** To fix this issue, it is recommended to apply a patch. The patch is available at commit `fcb0dbca0ec72b22fe0c9ddc8abc9cb188a0ff31`. As a temporary workaround, consider disabling the `downloadAndUnpackResource` function until a patch is applied. Restrict access to the ZIP File Handler component to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** com.github.samtools:htsjdk versions prior to 3.0.1 **Description** The issue arises from the `createTempDir()` function in `util/IOUtil.java` not checking for the existence of the temporary directory before attempting to create it, leading to the creation of temporary files in directories with insecure permissions. This is due to the `createTempDir()` function's behavior. **Recommendations** For versions prior to 3.0.1, update to version 3.0.1 or later to resolve the issue. As a temporary workaround, consider restricting access to the temporary directory to minimize the risk of exploitation.