C0Rydoras

**Name of the Vulnerable Software and Affected Versions** vm2 versions prior to 3.11.0 **Description** An issue exists where it is possible to obtain the host `Object`, allowing an attacker to escape the sandbox. This can be achieved through various methods, such as using the `getOwnPropertySymbols()` function of `HostObject` to obtain `Symbol(nodejs.util.inspect.custom)`, potentially leading to remote code execution. **Recommendations** Update to version 3.11.0.

**Name of the Vulnerable Software and Affected Versions** vm2 versions prior to 3.11.0 **Description** A sandbox escape allows unauthenticated attackers to execute arbitrary system commands (RCE) on the host. The issue occurs because `BaseHandler.getPrototypeOf` can be reached via `util.inspect`, enabling the retrieval of arbitrary prototypes. By manipulating object prototypes through internal bridge functions, an attacker can gain access to the host's process object. **Recommendations** Update to version 3.11.0.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.14.1 n8n versions prior to 2.13.3 n8n versions prior to 1.123.26 **Description** n8n is a workflow automation platform. A user authenticated with permissions to create or modify workflows could leverage the "Combine by SQL" mode within the Merge node to read local files on the n8n host and potentially achieve remote code execution. The AlaSQL sandbox lacked sufficient restrictions on certain SQL statements, enabling an attacker to access sensitive files on the server or compromise the instance. The vulnerable component is the Merge node and its use of AlaSQL. **Recommendations** Upgrade to n8n version 2.14.1 or later. Upgrade to n8n version 2.13.3 or later. Upgrade to n8n version 1.123.26 or later. If upgrading is not immediately possible, limit workflow creation and editing permissions to fully trusted users only. If upgrading is not immediately possible, disable the Merge node by adding `n8n-nodes-base.merge` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** SandboxJS versions prior to 0.8.34 **Description** SandboxJS is a JavaScript sandboxing library susceptible to a sandbox escape. The issue arises from the ability to obtain arrays containing the `Function` constructor. Combined with `Object.fromEntries`, this allows constructing objects with properties that can execute arbitrary code, leading to a complete escape of the sandbox. The provided Proof of Concept (PoC) demonstrates the exploitation of this issue using `process.getBuiltinModule("child process").execSync("ls", {stdio: "inherit"})` to execute system commands. The vulnerability can result in Remote Code Execution (RCE). The API endpoint is not explicitly mentioned. The vulnerable variable is `Function`. **Recommendations** Versions prior to 0.8.34 should be updated to version 0.8.34 or later.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.10.1 n8n versions prior to 2.9.3 n8n versions prior to 1.123.22 **Description** n8n is an open source workflow automation platform. An authenticated user with permission to create or modify workflows could exploit a weakness in the JavaScript Task Runner sandbox to execute code outside of its intended boundary. When using the default internal Task Runners, this could lead to a complete compromise of the n8n host system. If external Task Runners are in use, an attacker might gain access to or disrupt other tasks running on the Task Runner. The Task Runners must be enabled using the `N8N RUNNERS ENABLED=true` setting. Reports indicate over 100,000 servers are potentially affected, with a significant concentration in the United States and a notable presence in Russia. **Recommendations** Upgrade to n8n version 2.10.1 or later. Upgrade to n8n version 2.9.3 or later. Upgrade to n8n version 1.123.22 or later.

**Name of the Vulnerable Software and Affected Versions** Enclave versions prior to 2.11.1 **Description** Enclave is a secure JavaScript sandbox used for safe AI agent code execution. A critical security flaw exists in versions prior to 2.11.1, allowing an attacker to escape the sandbox boundaries and achieve remote code execution (RCE) on the underlying host system. This is possible due to the ability to obtain the native `Object` constructor, allowing access to restricted properties and host functions. Two proof-of-concept exploits are described, one leveraging ` host memory track ` when a memory limit is set, and another utilizing Node's `nodejs.util.inspect.custom` symbol when a memory limit is not set. Successful exploitation results in arbitrary command execution on the host, representing a full system compromise. **Recommendations** Upgrade to version 2.11.1 or later immediately.

**Name of the Vulnerable Software and Affected Versions** SandboxJS versions prior to 0.8.29 **Description** SandboxJS is a JavaScript sandboxing library affected by an issue where the return values of functions are not properly wrapped. This allows attackers to use `Object.values` or `Object.entries` to obtain an array containing the host's `Function` constructor. By utilizing `Array.prototype.at`, the host's `Function` constructor can be accessed, enabling the execution of arbitrary code outside of the sandbox. The provided proof-of-concept code demonstrates how to leverage this to execute commands like 'ls -lah' using the `child process` module. The vulnerability allows for sandbox escape, potentially leading to remote code execution (RCE). **Recommendations** Versions prior to 0.8.29 should be updated to version 0.8.29 or later.

**Name of the Vulnerable Software and Affected Versions** SandboxJS versions prior to 0.8.29 **Description** SandboxJS is a JavaScript sandboxing library. Prior to version 0.8.29, a flaw exists where the prototype of the `Map` object, present in `SAFE PROTOYPES`, can be accessed via `Map.prototype`. By overwriting the `Map.prototype.has` function, the sandbox can be escaped, potentially leading to remote code execution. The issue stems from a bug in the `let` implementation, where using `let` instead of `const` to declare a variable referencing `Map.prototype` results in `undefined`. This allows manipulation of the `Map.prototype.has` function. A proof-of-concept (PoC) demonstrates the ability to execute arbitrary commands, such as listing directory contents, by redefining `Map.prototype.has` to call `isFinite.constructor` with a malicious string. **Recommendations** Versions prior to 0.8.29 should be updated to version 0.8.29 to address this issue.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.4.8 **Description** n8n is a workflow automation platform. A flaw in the Python Code node allows authenticated users to bypass the Python sandbox and run code outside the intended security limits. The vulnerability allows for arbitrary code execution on the host system. **Recommendations** Update to version 2.4.8 or later.

**Name of the Vulnerable Software and Affected Versions** SandboxJS versions prior to 0.8.27 **Description** SandboxJS is a JavaScript sandboxing library with an issue where the ` lookupGetter ` function is not properly restricted. This can allow obtaining prototypes, potentially leading to sandbox escape and remote code execution. The issue affects versions prior to 0.8.27. **Recommendations** Update to SandboxJS version 0.8.27 or later.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 9.11.x through 9.11.10 Mattermost versions 10.4.x through 10.4.2 Mattermost versions 10.5.x through 10.5.0 **Description** The issue arises from the failure to properly validate the props used by the RetrospectivePost custom post type in the Playbooks plugin. This allows an attacker to create a specially crafted post with maliciously crafted props, causing a denial of service (DoS) of the web app for all users. **Recommendations** For versions 9.11.x through 9.11.10, update to a version later than 9.11.10 to resolve the issue. For versions 10.4.x through 10.4.2, update to a version later than 10.4.2 to resolve the issue. For versions 10.5.x through 10.5.0, update to a version later than 10.5.0 to resolve the issue. As a temporary workaround, consider disabling the RetrospectivePost custom post type in the Playbooks plugin until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 9.11.x through 9.11.5 Mattermost versions 10.0.x through 10.0.3 Mattermost versions 10.1.x through 10.1.3 Mattermost versions 10.2.x through 10.2.0 **Description** The issue arises from the improper handling of posts with attachments containing fields that cannot be cast to a String. This allows an attacker to cause the webapp to crash by creating and sending such a post to a channel. **Recommendations** For Mattermost versions 9.11.x through 9.11.5, update to a version later than 9.11.5 to resolve the issue. For Mattermost versions 10.0.x through 10.0.3, update to a version later than 10.0.3 to resolve the issue. For Mattermost versions 10.1.x through 10.1.3, update to a version later than 10.1.3 to resolve the issue. For Mattermost versions 10.2.x through 10.2.0, update to a version later than 10.2.0 to resolve the issue. As a temporary workaround, consider restricting the creation and sending of posts with attachments to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Mattermost Mobile versions <= 2.22.0 **Description** The issue allows an attacker to crash the mobile application via crafted malicious input. This is due to the failure to properly validate the style of proto supplied to an action's style in post.props.attachments. **Recommendations** For Mattermost Mobile versions <= 2.22.0, update to a version greater than 2.22.0 to resolve the issue. As a temporary workaround, consider restricting the use of attachments in posts to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Mattermost Mobile versions <=2.22.0 **Description** The issue arises from the improper handling of posts with attachments that contain fields which cannot be converted to a string. This allows an attacker to cause the mobile application to crash by creating and sending such a post to a channel. **Recommendations** For Mattermost Mobile versions <=2.22.0, update to a version higher than 2.22.0 to resolve the issue. As a temporary workaround, consider avoiding the use of attachments with fields that cannot be cast to a string in posts to prevent the application from crashing.

**Name of the Vulnerable Software and Affected Versions** Mattermost Mobile Apps versions <=2.22.0 **Description** The issue arises from the failure to properly validate post properties, allowing a malicious authenticated user to cause a crash via a malicious post. This can be exploited by an authenticated user, indicating a need for proper access controls and validation mechanisms. **Recommendations** For Mattermost Mobile Apps versions <=2.22.0, update to a version greater than 2.22.0 to resolve the issue. As a temporary workaround, consider restricting access to post properties to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 9.11.x through 9.11.5 Mattermost versions 10.0.x through 10.0.3 Mattermost versions 10.1.x through 10.1.3 Mattermost versions 10.2.x through 10.2.0 **Description** The issue arises from the failure to properly validate the style of proto supplied to an action's style in post.props.attachments. This allows an attacker to crash the frontend via crafted malicious input. **Recommendations** For versions 9.11.x through 9.11.5, consider disabling the processing of attachments in post.props until a patch is available. For versions 10.0.x through 10.0.3, restrict access to the post.props.attachments feature to minimize the risk of exploitation. For versions 10.1.x through 10.1.3, avoid using the style attribute in post.props.attachments until the issue is resolved. For versions 10.2.x through 10.2.0, as a temporary workaround, consider disabling the frontend when handling crafted malicious input until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 9.11.x through 9.11.5 Mattermost versions 10.0.x through 10.0.3 Mattermost versions 10.1.x through 10.1.3 Mattermost versions 10.2.x through 10.2.0 **Description** The issue is related to the improper validation of post properties, which allows a malicious authenticated user to cause a crash via a malicious post. This can be achieved through a public post, but specific details about the exploitation, such as API endpoints or vulnerable parameters, are not provided. **Recommendations** For Mattermost versions 9.11.x through 9.11.5, update to a version later than 9.11.5 to resolve the issue. For Mattermost versions 10.0.x through 10.0.3, update to a version later than 10.0.3 to resolve the issue. For Mattermost versions 10.1.x through 10.1.3, update to a version later than 10.1.3 to resolve the issue. For Mattermost versions 10.2.x through 10.2.0, update to a version later than 10.2.0 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 10.2.x through 10.2.0 Mattermost versions 9.11.x through 9.11.5 Mattermost versions 10.0.x through 10.0.3 Mattermost versions 10.1.x through 10.1.3 **Description** The issue arises from the failure to properly validate post properties, allowing a malicious authenticated user to cause a crash via a malicious post. This can be exploited by an authenticated user to disrupt the service. **Recommendations** For versions 10.2.x through 10.2.0, update to a version that properly validates post properties. For versions 9.11.x through 9.11.5, update to a version that properly validates post properties. For versions 10.0.x through 10.0.3, update to a version that properly validates post properties. For versions 10.1.x through 10.1.3, update to a version that properly validates post properties. As a temporary workaround, consider restricting access to post properties to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Mattermost Mobile Apps versions <=2.22.0 **Description** The issue arises from the failure to properly validate post properties, allowing a malicious authenticated user to cause a crash via a malicious post. This can be exploited by an authenticated user, indicating a need for proper validation mechanisms to prevent such crashes. **Recommendations** For Mattermost Mobile Apps versions <=2.22.0, update to a version greater than 2.22.0 to resolve the issue. As a temporary workaround, consider restricting the ability of authenticated users to create posts until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Mattermost versions 9.11.x through 9.11.5 Mattermost versions 10.0.x through 10.0.3 Mattermost versions 10.1.x through 10.1.3 Mattermost version 10.2.0 **Description** The issue is related to improper validation of post types in Mattermost, which allows attackers to deny service to users with the `sysconsole read plugins` permission. This can be achieved by creating a post with the `custom pl notification` type and specific properties. **Recommendations** For Mattermost versions 9.11.x through 9.11.5, update to a version newer than 9.11.5 to resolve the issue. For Mattermost versions 10.0.x through 10.0.3, update to a version newer than 10.0.3 to resolve the issue. For Mattermost versions 10.1.x through 10.1.3, update to a version newer than 10.1.3 to resolve the issue. For Mattermost version 10.2.0, update to a version newer than 10.2.0 to resolve the issue. As a temporary workaround, consider restricting the use of the `custom pl notification` post type to minimize the risk of exploitation.