Yadhukrishnam

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.17 n8n versions prior to 2.5.2 **Description** n8n is an open-source workflow automation platform. An authenticated user with permission to create or modify workflows can exploit crafted expressions in workflow parameters to trigger system command execution on the host running n8n. This allows for potential full server compromise, including the theft of API keys, credentials, and secrets. The issue stems from an expression escape vulnerability and incomplete AST-based sanitization. Public exploits are available. **Recommendations** Upgrade to n8n version 1.123.17 or later. Upgrade to n8n version 2.5.2 or later. As a temporary workaround, limit workflow creation and editing permissions to fully trusted users only. Deploy n8n in a hardened environment with restricted operating system privileges and network access.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.10 n8n versions prior to 2.5.0 **Description** n8n, an open source workflow automation platform, contains a flaw in the Git node. This allows authenticated users with create or modify permissions for workflows to execute arbitrary system commands or read arbitrary files on the n8n host. The issue impacts systems where users have the ability to create or modify workflows. No information is available regarding the number of potentially affected devices worldwide or any real-world incidents of exploitation. The Git node is a component used for interacting with Git repositories. The `Git node` allows users to perform actions such as cloning, pulling, and pushing changes to Git repositories. **Recommendations** Upgrade to n8n version 1.123.10 or later. Upgrade to n8n version 2.5.0 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, restrict or disable access to the Git node if it is not essential for operations. If upgrading is not immediately possible, deploy n8n in a hardened environment with restricted operating system privileges and network access.

**Name of the Vulnerable Software and Affected Versions** Hoppscotch Browser Extension versions prior to 0.35 **Description** The issue arises from an oversight in the Hoppscotch Browser Extension, allowing messages to be sent and processed from unauthorized origins. This exposes users to potential security risks, as any site running on the browser with the extension installed can bypass CORS restrictions. The vulnerability can lead to improper validation of integrity check values, potentially resulting in system compromise. **Recommendations** For versions prior to 0.35, upgrade to version 0.35 or later to resolve the issue. As a temporary workaround for Chrome users, consider disabling the extension access to only the origins that you want through the Extensions Settings. For Firefox users, upgrade to a fixed version, as there is no alternative workaround available.

**Name of the Vulnerable Software and Affected Versions** D-Tale versions prior to 3.7.0 **Description** The issue allows remote code execution, enabling attackers to run malicious code on the server. This is particularly concerning for users hosting D-Tale publicly. The estimated number of potentially affected devices worldwide is not specified. There is no information provided about real-world incidents where this issue was exploited. **Recommendations** For versions prior to 3.7.0, the only workaround is to host D-Tale to trusted users. For all affected versions, upgrade to version 3.7.0, where the "Custom Filter" input is turned off by default, to fully resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Node.js versions v16 through v20 **Description** The issue is related to the llhttp parser in the http module, which does not strictly use the CRLF sequence to delimit HTTP requests, leading to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser, contrary to RFC7230 section 3, which states that only the CRLF sequence should delimit each header-field. **Recommendations** For Node.js versions v16 through v20, at the moment, there is no information about a newer version that contains a fix for this vulnerability.