Skay

**Name of the Vulnerable Software and Affected Versions** Apache Solr versions 8.10.0 through 8.11.2 Apache Solr versions 9.0.0 through 9.2.x **Description** The issue is related to an Incorrect Permission Assignment for Critical Resource and Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr. The Schema Designer feature was introduced to allow users to more easily configure and test new Schemas and configSets. However, when the feature was created, the "trust" (authentication) of these configSets was not considered, allowing configSets created by unauthenticated users to load external libraries when used in the Schema Designer. This could potentially lead to Remote Code Execution. **Recommendations** For Apache Solr versions 8.10.0 through 8.11.2, upgrade to version 8.11.3. For Apache Solr versions 9.0.0 through 9.2.x, upgrade to version 9.3.0.

**Name of the Vulnerable Software and Affected Versions** Zimbra ZCS version 8.8.15 **Description** The issue is a Cross Site Scripting vulnerability that allows a remote authenticated attacker to execute arbitrary code via a crafted script to the "/h/autoSaveDraft" function. This vulnerability is actively exploited by hackers. **Recommendations** For Zimbra ZCS version 8.8.15, consider disabling the `/h/autoSaveDraft` function as a temporary workaround until a patch is available. Restrict access to this function 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** Apache OFBiz versions prior to 18.12.07 **Description** The issue is an arbitrary file reading vulnerability in Apache OFBiz when using the Solr plugin. This is a pre-authentication attack, meaning it can be exploited without needing to authenticate first. **Recommendations** For versions prior to 18.12.07, update to version 18.12.07 or later to resolve the issue. As a temporary workaround, consider disabling the Solr plugin until a patch is available. Restrict access to sensitive files and directories to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Zoho ManageEngine ADSelfService Plus versions through 6203 **Description** The issue allows for a brute-force attack, leading to a password reset on IDM applications. This is a result of a weakness in the password reset mechanism, which can be exploited by an attacker to gain unauthorized access. **Recommendations** For Zoho ManageEngine ADSelfService Plus versions through 6203, consider implementing additional security measures to prevent brute-force attacks, such as rate limiting or IP blocking, until a patch is available. As a temporary workaround, restrict access to the password reset feature to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Cisco Unified Communications Manager versions 11.5(1) through 14 Cisco Unified Communications Manager Session Management Edition versions 11.5(1) through 14 **Description** The issue is related to errors in processing input data in the web interface of the affected systems, allowing an authenticated, remote attacker to conduct SQL injection attacks. This could enable the attacker to read or modify any data on the underlying database or elevate their privileges. The vulnerability exists because the web-based management interface inadequately validates user input. **Recommendations** For Cisco Unified Communications Manager versions 11.5(1) through 12.5(1), update to version 12.5(1)SU7. For Cisco Unified Communications Manager version 14, update to version 14SU3, which is scheduled for release in March 2023. As a temporary workaround, consider restricting access to the web-based management interface to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Zoho ManageEngine ADSelfService Plus versions prior to 6203 **Description** The issue allows for a denial of service, resulting in an application restart, via a crafted payload sent to the "Mobile App Deployment API" endpoint. **Recommendations** For versions prior to 6203, update to version 6203 or later to resolve the issue. As a temporary workaround, consider restricting access to the Mobile App Deployment API endpoint until the update is applied.