Reginaldo Silva

**Name of the Vulnerable Software and Affected Versions** (affected versions not specified) **Description** The vulnerability involves an unspecified issue. There is no information about the number of potentially affected devices or any real-world incidents where this issue was exploited. **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** Apache OpenOffice versions through 4.1.15 **Description** Apache OpenOffice Calc spreadsheets can include links to external files, known as "external data sources". A missing authorization check in Apache OpenOffice allowed an attacker to create a document that would load these links without user confirmation. **Recommendations** Upgrade to version 4.1.16 to resolve this issue.

**Name of the Vulnerable Software and Affected Versions** LibreOffice (affected versions not specified) **Description** The issue is related to insufficient macro permission validation, allowing an attacker to execute built-in macros without warning. In affected versions, LibreOffice supports hyperlinks with macro or similar built-in command targets that can be executed when activated without warning the user. This could potentially enable a remote attacker to execute arbitrary code by embedding a malicious macro in a document. **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** LibreOffice (affected versions not specified) **Description** The issue is related to improper input validation in the GStreamer integration of LibreOffice, allowing an attacker to execute arbitrary GStreamer plugins. In affected versions, the filename of the embedded video is not sufficiently escaped when passed to GStreamer, enabling an attacker to run arbitrary gstreamer plugins depending on what plugins are installed on the target system. **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** Metabase versions prior to 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, and 1.46.6.4 **Description** The issue is related to the incorrect management of code generation in the Metabase platform, which could allow remote code execution on the server. The core problem is that the embedded in-memory database H2 exposes ways for a connection string to include code that is then executed by the process running the embedded database. This means a user-supplied string can be used to inject executable code. The validation API, which can be called without validation, is the primary vector used for exploitation. Approximately 58,710 results are potentially affected. **Recommendations** To resolve the issue, update to versions 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, or 1.46.6.4, which fix the issue by removing the ability to add H2 databases entirely. As a temporary workaround, block the endpoints `POST /api/database`, `PUT /api/database/:id`, and `POST /api/setup/validateuntil` at the network level. Those who use H2 as a file-based database should migrate to SQLite.

**Name of the Vulnerable Software and Affected Versions** Redis versions prior to the fixed version Debian-specific Redis Server (affected versions not specified) **Description** A Lua sandbox escape vulnerability in Redis could result in remote code execution. The issue is related to a packaging problem and is specific to Debian. It is estimated that around 40,000 out of 360,000 Redis instances are unprotected, with some being vulnerable to this issue. The vulnerability has been exploited in real-world attacks, including by the P2PInfect malware, which targets IoT devices and employs evasion methods. The malware uses the vulnerability to escape the Lua sandbox and execute arbitrary code, then establishes a peer-to-peer connection with a larger network and downloads additional malicious binaries. **Recommendations** For Redis versions prior to the fixed version, update to the latest version to mitigate the risk. As a temporary workaround, consider disabling the `eval()` function until a patch is available. Restrict access to the Redis server to minimize the risk of exploitation. Set strong passwords and keep the software up to date. Avoid using the vulnerable Lua sandbox until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.