Leesh3288

**Name of the Vulnerable Software and Affected Versions:** Redis versions 2.8 through 8.0.3, 7.4.5, 7.2.10, and 6.2.19. Valkey versions up to 8.1.3 and 8.0.4 are also affected. **Description:** Redis and Valkey are vulnerable to a heap-based buffer overflow in the HyperLogLog functionality. An authenticated attacker can exploit this vulnerability by sending a specially crafted string, potentially leading to remote code execution (RCE). The root cause is an integer overflow in the `hllMerge()` function when processing sparse HyperLogLog data, leading to an out-of-bounds write. A Proof-of-Concept (PoC) exploit is available. The vulnerability affects versions 2.8 and later of Redis, up to and including 8.0.3, 7.4.5, 7.2.10, and 6.2.19. Valkey versions up to 8.1.3 and 8.0.4 are also impacted. **Recommendations:** - Upgrade Redis to version 8.0.3 or later, 7.4.5 or later, 7.2.10 or later, or 6.2.19 or later. - Upgrade Valkey to version 8.1.3 or 8.0.4 or later. - As a temporary mitigation, restrict access to HyperLogLog commands using ACLs: `ACL SETUSER username -pfadd -pfcount -pfmerge`. - Monitor for anomalous HyperLogLog operations, unexpected crashes, and unusual network traffic. - Limit network access to Redis and Valkey instances to trusted sources and implement robust authentication mechanisms.

**Name of the Vulnerable Software and Affected Versions** Deno versions prior to 1.43 **Description** The Deno sandbox may be unexpectedly weakened by allowing file read/write access to privileged files in various locations on Unix and Windows platforms. For example, reading `/proc/self/environ` may provide access equivalent to `--allow-env`, and writing `/proc/self/mem` may provide access equivalent to `--allow-all`. Users who grant read and write access to the entire filesystem may not realize that these accesses to these files may have additional, unintended consequences. **Recommendations** For Deno versions prior to 1.43, consider adding explicit deny flags to restrict access to sensitive files, such as `--deny-read=/dev`, `--deny-read=/sys`, `--deny-read=/proc`, `--deny-read=/etc`, `--deny-write=/dev`, `--deny-write=/sys`, `--deny-write=/proc`, and `--deny-write=/etc`. Note that symlinks in allowed locations may defeat this protection in earlier versions of Deno. For Deno 1.43 and above, ensure explicit `--allow-all` access is required to read or write `/etc`, `/dev` on Unix platforms, as well as `/proc` and `/sys` on Linux platforms, and any path starting with `` on Windows.

**Name of the Vulnerable Software and Affected Versions** Deno version 1.39.0 **Description** The issue arises from the use of raw file descriptors in `op node ipc pipe()`, leading to the premature close of arbitrary file descriptors. This allows standard input to be closed and re-opened as a different resource, resulting in a permission prompt bypass. An attacker controlling the code executed inside a Deno runtime can exploit this to obtain arbitrary code execution on the host machine, regardless of permissions. The vulnerability is known to be exploitable, with a working exploit that achieves arbitrary code execution by bypassing prompts from zero permissions and abusing the lack of filesystem permission checks in the Cache API. The attack can be conducted silently as stderr can also be closed, suppressing all prompt outputs. **Recommendations** To resolve the issue, update to Deno version 1.39.1, which fixes the bug. For version 1.39.0, as a temporary workaround, consider restricting the use of the `op node ipc pipe()` function until a patch is available. Additionally, be cautious when using the Cache API, as it lacks filesystem permission checks, which can be abused in conjunction with this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Deno versions 1.36.2 through 1.40.3 **Description** The issue arises from the use of inherently unsafe `*const c void` and `ExternalPointer` which leads to use-after-free access of the underlying structure, resulting in arbitrary code execution. An attacker controlling the code executed inside a Deno runtime can exploit this to obtain arbitrary code execution on the host machine regardless of permissions. The vulnerability is known to be exploitable for both `*const c void` and `ExternalPointer` implementations. **Recommendations** For Deno versions 1.36.2 through 1.40.2, update to version 1.40.3 to fix the issue. For Deno versions prior to 1.36.2, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, consider restricting the use of `*const c void` and `ExternalPointer` to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** vm2 versions up to and including 3.9.19 **Description** The issue in vm2 allows attackers to escape the sandbox and run arbitrary code, potentially resulting in Remote Code Execution. This is possible due to the Node.js custom inspect function. There is no information about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited. The vulnerability exists because of the lack of measures to neutralize special elements used in the operating system command. **Recommendations** For versions up to and including 3.9.19, as a temporary workaround, consider disabling the custom inspect function until a patch is available. However, since there are no patches and no known workarounds, users are advised to find an alternative software. Avoid using the vm2 sandbox for emulation until the issue is resolved.