Lukas Euler

**Name of the Vulnerable Software and Affected Versions** Lodash versions 4.0.0 through 4.17.22 **Description** Lodash versions 4.0.0 through 4.17.22 are susceptible to prototype pollution within the ` .unset` and ` .omit` functions. An attacker can leverage crafted paths to trigger the deletion of methods from global prototypes. The issue allows for property deletion but does not permit modification of the original behavior of those properties. **Recommendations** Update to Lodash version 4.17.23 or later.

**Name of the Vulnerable Software and Affected Versions** travel-support-program versions prior to the patched version **Description** The travel-support-program, a rails app supporting the openSUSE travel support program, is affected by a Ransack query injection issue. This allows sensitive user data, including bank account details and password hashes, to be extracted. The issue is exploited through the `* start`, `* end`, or `* cont` search matchers in the Ransack library, using character-by-character brute-force. A single bank account number can be extracted with less than 200 requests, and a password hash can be extracted with approximately 1200 requests, all within a few minutes. **Recommendations** To resolve the issue, apply the patch committed in d22916275c51500b4004933ff1b0a69bc807b2b7. Alternatively, cherry-pick the patch, but ensure you have also applied the Rails 5.0 migration done in #150, including its dependent pull requests. As a temporary workaround, consider restricting access to the Ransack search functionality until the patch is applied.

**Name of the Vulnerable Software and Affected Versions** Microsoft Office (affected versions not specified) **Description** The issue is related to incorrect code generation management in Microsoft Office. It allows a remote attacker to execute arbitrary code. **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 prior to 4.1.10 **Description** The issue is related to the handling of non-http(s) hyperlinks in Apache OpenOffice, which can lead to untrusted code execution if a link is specifically crafted. This problem has existed since about 2006. It is recommended to be careful when opening documents from unknown and unverified sources. **Recommendations** For versions prior to 4.1.10, consider avoiding the use of non-http(s) hyperlinks in documents until a patch is available. As a temporary workaround, users should exercise caution when opening documents from unknown sources and avoid clicking on suspicious links. In the upcoming version 4.1.10, a security warning will be displayed when opening potentially dangerous hyperlinks, giving the user the option to continue or cancel the action.

**Name of the Vulnerable Software and Affected Versions** LibreOffice versions prior to 7.1.2 LibreOffice versions prior to 7.0.5 **Description** The issue is related to errors in security settings, allowing a remote attacker to impact the confidentiality, integrity, and availability of protected information. This can be achieved by manipulating a link to circumvent the denylist, resulting in ShellExecute attempting to launch an executable type. **Recommendations** For versions prior to 7.1.2, update to version 7.1.2 or later. For versions prior to 7.0.5, update to version 7.0.5 or later.

Name of the Vulnerable Software and Affected Versions: Wireshark versions 3.2.0 through 3.2.11 Wireshark versions 3.4.0 through 3.4.3 Description: The issue is related to improper URL handling, which could allow remote code execution via packet injection or crafted capture files. Recommendations: For Wireshark versions 3.2.0 through 3.2.11, update to a version outside of this range to resolve the issue. For Wireshark versions 3.4.0 through 3.4.3, update to a version outside of this range to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** OpenStack blazar-dashboard versions prior to 1.3.1 OpenStack blazar-dashboard version 2.0.0 OpenStack blazar-dashboard version 3.0.0 **Description** An issue in OpenStack blazar-dashboard allows a user with access to the Blazar dashboard in Horizon to trigger code execution on the Horizon host. This is due to the use of the Python `eval` function, which may result in unauthorized access to the Horizon host and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected. **Recommendations** For OpenStack blazar-dashboard versions prior to 1.3.1, update to version 1.3.1 or later. For OpenStack blazar-dashboard version 2.0.0, update to a version later than 2.0.0. For OpenStack blazar-dashboard version 3.0.0, update to a version later than 3.0.0. As a temporary workaround, consider restricting access to the Blazar dashboard in Horizon to minimize the risk of exploitation.