Bahaa Naamneh

**Name of the Vulnerable Software and Affected Versions** .NET versions (affected versions not specified) **Description** The issue is related to pointer dereference errors in the Microsoft .NET platform. Exploitation of this issue can allow a remote attacker to cause a denial of service. **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** Trellix Anti-Malware Engine versions prior to January 2024 release **Description** A symbolic link manipulation issue allows an authenticated local user to potentially gain an escalation of privileges. This is achieved by adding an entry to the registry under the Trellix ENS registry folder with a symbolic link to files that the user wouldn't normally have permission to. After a scan, the Engine would follow the links and remove the files. **Recommendations** For versions prior to the January 2024 release, update to the January 2024 release or later to resolve the issue. As a temporary workaround, consider restricting access to the Trellix ENS registry folder to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** OpenSSL versions prior to 3.2 (excluding FIPS modules in 3.2, 3.1, and 3.0) **Description** The issue arises from the improper handling of NULL fields in PKCS12 files, leading to a potential Denial of Service attack. Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly due to a NULL pointer dereference. The affected OpenSSL APIs are: `PKCS12 parse()`, `PKCS12 unpack p7data()`, `PKCS12 unpack p7encdata()`, `PKCS12 unpack authsafes()`, and `PKCS12 newpass()`. **Recommendations** As a temporary workaround, consider disabling the use of `PKCS12 parse()`, `PKCS12 unpack p7data()`, `PKCS12 unpack p7encdata()`, `PKCS12 unpack authsafes()`, and `PKCS12 newpass()` functions until a patch is available. Restrict access to PKCS12 files from untrusted sources to minimize the risk of exploitation. 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** Google Chrome versions prior to 118.0.5993.70 **Description** The issue is related to an inappropriate implementation in the Installer component of Google Chrome, which allowed a local attacker to bypass discretionary access control via a crafted command. This could potentially enable an attacker to circumvent existing security restrictions. The vulnerability is related to incorrectly implemented security checks for standard elements, and exploitation may allow a remote attacker to bypass security restrictions using a specially crafted HTML page. **Recommendations** For Google Chrome versions prior to 118.0.5993.70, update to version 118.0.5993.70 or later to resolve the issue. As a temporary workaround, consider restricting access to the Installer component until a patch is available. Avoid using the Installer component with crafted commands until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Trend Micro Apex One (affected versions not specified) Trend Micro Apex One as a Service (affected versions not specified) **Description** A privilege escalation issue could allow a local attacker to unintentionally delete privileged Trend Micro registry keys, including its own protected registry keys, on affected installations. **Recommendations** For Trend Micro Apex One, at the moment, there is no information about a newer version that contains a fix for this vulnerability. For Trend Micro Apex One as a Service, 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** Microsoft Word versions prior to 10.2627.6714 for Macintosh Microsoft Word 2002 before SP3 **Description** A buffer overflow issue exists, allowing remote attackers to cause a denial of service and possibly execute arbitrary code via a crafted mcw file. **Recommendations** For Microsoft Word for Macintosh version 10.2627.6714 and earlier, update to a version later than 10.2627.6714. For Microsoft Word 2002, apply Service Pack 3 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** RUMBA versions 7.3 and earlier **Description** The issue is related to multiple buffer overflows that can be triggered by remote attackers using crafted values in a profile file. This can lead to a denial of service and potentially allow the execution of arbitrary code. An example of such exploitation is through the use of a long `SysName` field. **Recommendations** For versions 7.3 and earlier, consider applying configuration changes to restrict access to profile files until a fix is available. As a temporary workaround, restrict the length of the `SysName` field to prevent buffer overflows.

Name of the Vulnerable Software and Affected Versions: Escapade Scripting Engine (ESP) (affected versions not specified) Description: A cross-site scripting (XSS) issue exists, allowing remote attackers to inject arbitrary script via the `method` parameter. This can be demonstrated using the `PAGE` parameter. 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: FTP Desktop client versions 3.5 and earlier Description: The issue is related to multiple heap-based buffer overflows that can be triggered by remote malicious servers. This can occur through a long FTP banner, a long response to a `USER` command, or a long response to a `PASS` command. This allows the malicious server to execute arbitrary code. Recommendations: For FTP Desktop client versions 3.5 and earlier, 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: Escapade Scripting Engine (ESP) (affected versions not specified) Description: The issue allows remote attackers to obtain sensitive path information via a malformed request. This is achieved by exploiting the `PAGE` parameter, which leaks the information in an error message. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.