Yuyang Xiao

**Name of the Vulnerable Software and Affected Versions** CloudStack versions prior to 4.18.1.1 CloudStack versions prior to 4.19.0.1 **Description** The CloudStack management server honors the `x-forwarded-for` HTTP header and logs it as the source IP of an API request by default. This could lead to authentication bypass and other operational problems if an attacker spoofs their IP address. **Recommendations** For versions prior to 4.18.1.1, upgrade to CloudStack version 4.18.1.1. For versions prior to 4.19.0.1, upgrade to CloudStack version 4.19.0.1.

**Name of the Vulnerable Software and Affected Versions** CloudStack versions prior to 4.18.1.1 CloudStack versions prior to 4.19.0.1 **Description** The CloudStack management server and secondary storage VM could be tricked into making requests to restricted or random resources by means of following 301 HTTP redirects presented by external servers when downloading templates or ISOs. **Recommendations** For versions prior to 4.18.1.1, upgrade to version 4.18.1.1 to fix the issue. For versions prior to 4.19.0.1, upgrade to version 4.19.0.1 to fix the issue.

Name of the Vulnerable Software and Affected Versions: Apache Solr versions 6.0.0 through 6.6.4 Apache Solr versions 7.0.0 through 7.3.1 Description: The issue relates to an XML external entity expansion (XXE) in Solr config files, such as `currency.xml`, `enumsConfig.xml`, and TIKA parsecontext config file, which can be exploited to read arbitrary local files from the Solr server or the internal network using file/ftp/http protocols. The Xinclude functionality in these config files is also affected. The manipulated files can be uploaded as configsets using Solr's API. Recommendations: For Apache Solr versions 6.0.0 through 6.6.4, update to a version outside of this range to mitigate the risk. For Apache Solr versions 7.0.0 through 7.3.1, update to a version outside of this range to mitigate the risk. As a temporary workaround, consider restricting access to the Solr API to minimize the risk of exploitation. Avoid using the Xinclude functionality in Solr config files until the issue is resolved.