Vulnerabilities (CVE)

Filtered by vendor Open-xchange Subscribe
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2023-26442 1 Open-xchange 1 Open-xchange Appsuite Office 2024-01-12 N/A 3.2 LOW
In case Cacheservice was configured to use a sproxyd object-storage backend, it would follow HTTP redirects issued by that backend. An attacker with access to a local or restricted network with the capability to intercept and replay HTTP requests to sproxyd (or who is in control of the sproxyd service) could perform a server-side request-forgery attack and make Cacheservice connect to unexpected resources. We have disabled the ability to follow HTTP redirects when connecting to sproxyd resources. No publicly available exploits are known.
CVE-2023-26438 1 Open-xchange 1 Open-xchange Appsuite Backend 2024-01-12 N/A 3.1 LOW
External service lookups for a number of protocols were vulnerable to a time-of-check/time-of-use (TOCTOU) weakness, involving the JDK DNS cache. Attackers that were timing DNS cache expiry correctly were able to inject configuration that would bypass existing network deny-lists. Attackers could exploit this weakness to discover the existence of restricted network infrastructure and service availability. Improvements were made to include deny-lists not only during the check of the provided connection data, but also during use. No publicly available exploits are known.
CVE-2023-26427 1 Open-xchange 1 Open-xchange Appsuite Backend 2024-01-12 N/A 3.3 LOW
Default permissions for a properties file were too permissive. Local system users could read potentially sensitive information. We updated the default permissions for noreply.properties set during package installation. No publicly available exploits are known.
CVE-2019-11806 1 Open-xchange 1 Open-xchange Appsuite 2020-08-24 2.1 LOW 3.3 LOW
OX App Suite 7.10.1 and earlier has Insecure Permissions.
CVE-2016-4027 1 Open-xchange 1 Open-xchange Appsuite 2018-10-19 3.5 LOW 3.5 LOW
An issue was discovered in Open-Xchange OX App Suite before 7.8.1-rev10. App Suite frontend offers to control whether a user wants to store cookies that exceed the session duration. This functionality is useful when logging in from clients with reduced privileges or shared environments. However the setting was incorrectly recognized and cookies were stored regardless of this setting when the login was performed using a non-interactive login method. In case the setting was enforced by middleware configuration or the user went through the interactive login page, the workflow was correct. Cookies with authentication information may become available to other users on shared environments. In case the user did not properly log out from the session, third parties with access to the same client can access a user's account.