Timo Schmid

**Name of the Vulnerable Software and Affected Versions** Node.js versions 6.x and later **Description** The issue allows for a DNS rebinding attack, potentially leading to remote code execution. This can be exploited by malicious websites open in a web browser on the same computer or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to bypass same-origin-policy checks, allowing HTTP connections to localhost or hosts on the local network. If a Node.js process with the debug port active is running, the malicious website could connect to it as a debugger and gain full code execution access. **Recommendations** For Node.js versions 6.x and later, consider disabling the debug port to prevent exploitation until a fix is available. Restrict access to the Node.js inspector to minimize the risk of exploitation. Avoid opening malicious websites while running a Node.js process with the debug port active. 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** git versions 2.4.12 and earlier, 2.5.x through 2.5.5, 2.6.x through 2.6.6, 2.7.x through 2.7.4, 2.8.x through 2.8.4, 2.9.x through 2.9.3, 2.10.x through 2.10.2, 2.11.x through 2.11.1, 2.12.x through 2.12.2 **Description** The issue allows remote authenticated users to gain privileges via a repository name that starts with a - (dash) character. **Recommendations** For git versions 2.4.12 and earlier, update to version 2.4.12 or later. For git versions 2.5.x through 2.5.5, update to version 2.5.6 or later. For git versions 2.6.x through 2.6.6, update to version 2.6.7 or later. For git versions 2.7.x through 2.7.4, update to version 2.7.5 or later. For git versions 2.8.x through 2.8.4, update to version 2.8.5 or later. For git versions 2.9.x through 2.9.3, update to version 2.9.4 or later. For git versions 2.10.x through 2.10.2, update to version 2.10.3 or later. For git versions 2.11.x through 2.11.1, update to version 2.11.2 or later. For git versions 2.12.x through 2.12.2, update to version 2.12.3 or later.

**Name of the Vulnerable Software and Affected Versions** Gogs (aka Go Git Service) versions 0.3.1-9 through 0.5.6.x **Description** The issue is related to a SQL injection vulnerability. It allows remote attackers to execute arbitrary SQL commands via the `label` parameter to user/repos/issues. The vulnerability is due to improper sanitization of user input, making certain methods vulnerable to SQL injection if used with unsanitized user input. **Recommendations** For Gogs (aka Go Git Service) versions 0.3.1-9 through 0.5.6.x, update to version 0.5.6.1025 Beta or later to resolve the issue. As a temporary workaround, consider sanitizing user input before passing it to vulnerable methods, such as the GetIssues function in models/issue.go. Restrict access to the `label` parameter in the user/repos/issues endpoint to minimize the risk of exploitation.