Filtered by vendor Open-xchange
Subscribe
Total
252 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2023-41704 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 6.1 MEDIUM |
Processing of CID references at E-Mail can be abused to inject malicious script code that passes the sanitization engine. Malicious script code could be injected to a users sessions when interacting with E-Mails. Please deploy the provided updates and patch releases. CID handing has been improved and resulting content is checked for malicious content. No publicly available exploits are known. | |||||
CVE-2023-41705 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 6.5 MEDIUM |
Processing of user-defined DAV user-agent strings is not limited. Availability of OX App Suite could be reduced due to high processing load. Please deploy the provided updates and patch releases. Processing time of DAV user-agents now gets monitored, and the related request is terminated if a resource threshold is reached. No publicly available exploits are known. | |||||
CVE-2023-41706 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 6.5 MEDIUM |
Processing time of drive search expressions now gets monitored, and the related request is terminated if a resource threshold is reached. Availability of OX App Suite could be reduced due to high processing load. Please deploy the provided updates and patch releases. Processing of user-defined drive search expressions is not limited No publicly available exploits are known. | |||||
CVE-2023-41707 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 6.5 MEDIUM |
Processing of user-defined mail search expressions is not limited. Availability of OX App Suite could be reduced due to high processing load. Please deploy the provided updates and patch releases. Processing time of mail search expressions now gets monitored, and the related request is terminated if a resource threshold is reached. No publicly available exploits are known. | |||||
CVE-2023-41708 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 5.4 MEDIUM |
References to the "app loader" functionality could contain redirects to unexpected locations. Attackers could forge app references that bypass existing safeguards to inject malicious script code. Please deploy the provided updates and patch releases. References to apps are now controlled more strict to avoid relative references. No publicly available exploits are known. | |||||
CVE-2023-41703 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-10-17 | N/A | 6.1 MEDIUM |
User ID references at mentions in document comments were not correctly sanitized. Script code could be injected to a users session when working with a malicious document. Please deploy the provided updates and patch releases. User-defined content like comments and mentions are now filtered to avoid potentially malicious content. No publicly available exploits are known. | |||||
CVE-2023-41710 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 5.4 MEDIUM |
User-defined script code could be stored for a upsell related shop URL. This code was not correctly sanitized when adding it to DOM. Attackers could lure victims to user accounts with malicious script code and make them execute it in the context of a trusted domain. We added sanitization for this content. No publicly available exploits are known. | |||||
CVE-2023-29050 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 9.6 CRITICAL |
The optional "LDAP contacts provider" could be abused by privileged users to inject LDAP filter strings that allow to access content outside of the intended hierarchy. Unauthorized users could break confidentiality of information in the directory and potentially cause high load on the directory server, leading to denial of service. Encoding has been added for user-provided fragments that are used when constructing the LDAP query. No publicly available exploits are known. | |||||
CVE-2023-29049 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 6.1 MEDIUM |
The "upsell" widget at the portal page could be abused to inject arbitrary script code. Attackers that manage to lure users to a compromised account, or gain temporary access to a legitimate account, could inject script code to gain persistent code execution capabilities under a trusted domain. User input for this widget is now sanitized to avoid malicious content the be processed. No publicly available exploits are known. | |||||
CVE-2023-29051 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 8.1 HIGH |
User-defined OXMF templates could be used to access a limited part of the internal OX App Suite Java API. The existing switch to disable the feature by default was not effective in this case. Unauthorized users could discover and modify application state, including objects related to other users and contexts. We now make sure that the switch to disable user-generated templates by default works as intended and will remove the feature in future generations of the product. No publicly available exploits are known. | |||||
CVE-2023-29052 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 5.4 MEDIUM |
Users were able to define disclaimer texts for an upsell shop dialog that would contain script code that was not sanitized correctly. Attackers could lure victims to user accounts with malicious script code and make them execute it in the context of a trusted domain. We added sanitization for this content. No publicly available exploits are known. | |||||
CVE-2023-29048 | 1 Open-xchange | 1 Ox App Suite | 2024-02-28 | N/A | 8.8 HIGH |
A component for parsing OXMF templates could be abused to execute arbitrary system commands that would be executed as the non-privileged runtime user. Users and attackers could run system commands with limited privilege to gain unauthorized access to confidential information and potentially violate integrity by modifying resources. The template engine has been reconfigured to deny execution of harmful commands on a system level. No publicly available exploits are known. | |||||
CVE-2023-26453 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-02-28 | N/A | 8.8 HIGH |
Requests to cache an image could be abused to include SQL queries that would be executed unchecked. Exploiting this vulnerability requires at least access to adjacent networks of the imageconverter service, which is not exposed to public networks by default. Arbitrary SQL statements could be executed in the context of the services database user account. API requests are now properly checked for valid content and attempts to circumvent this check are being logged as error. No publicly available exploits are known. | |||||
CVE-2023-29047 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-02-28 | N/A | 7.3 HIGH |
Imageconverter API endpoints provided methods that were not sufficiently validating and sanitizing client input, allowing to inject arbitrary SQL statements. An attacker with access to the adjacent network and potentially API credentials, could read and modify database content which is accessible to the imageconverter SQL user account. None No publicly available exploits are known. | |||||
CVE-2023-26440 | 1 Open-xchange | 1 Open-xchange Appsuite Office | 2024-02-28 | N/A | 7.8 HIGH |
The cacheservice API could be abused to indirectly inject parameters with SQL syntax which was insufficiently sanitized and would later be executed when creating new cache groups. Attackers with access to a local or restricted network could perform arbitrary SQL queries. We have improved the input check for API calls and filter for potentially malicious content. No publicly available exploits are known. | |||||
CVE-2023-26456 | 1 Open-xchange | 1 Ox Guard | 2024-02-28 | N/A | 5.4 MEDIUM |
Users were able to set an arbitrary "product name" for OX Guard. The chosen value was not sufficiently sanitized before processing it at the user interface, allowing for indirect cross-site scripting attacks. Accounts that were temporarily taken over could be configured to trigger persistent code execution, allowing an attacker to build a foothold. Sanitization is in place for product names now. No publicly available exploits are known. | |||||
CVE-2023-26451 | 1 Open-xchange | 1 Open-xchange Appsuite Backend | 2024-02-28 | N/A | 7.5 HIGH |
Functions with insufficient randomness were used to generate authorization tokens of the integrated oAuth Authorization Service. Authorization codes were predictable for third parties and could be used to intercept and take over the client authorization process. As a result, other users accounts could be compromised. The oAuth Authorization Service is not enabled by default. We have updated the implementation to use sources with sufficient randomness to generate authorization tokens. No publicly available exploits are known. | |||||
CVE-2023-29044 | 1 Open-xchange | 1 Open-xchange Appsuite | 2024-02-28 | N/A | 5.4 MEDIUM |
Documents operations could be manipulated to contain invalid data types, possibly script code. Script code could be injected to an operation that would be executed for users that are actively collaborating on the same document. Operation data exchanged between collaborating parties does now get escaped to avoid code execution. No publicly available exploits are known. | |||||
CVE-2023-26446 | 1 Open-xchange | 1 Open-xchange Appsuite Frontend | 2024-02-28 | N/A | 5.4 MEDIUM |
The users clientID at "application passwords" was not sanitized or escaped before being added to DOM. Malicious script code can be executed within the victims context. This can lead to session hijacking or triggering unwanted actions via the web interface and API. To exploit this an attacker would require temporary access to the users account or lure a user to a compromised account. We now sanitize the user-controllable clientID parameter. No publicly available exploits are known. | |||||
CVE-2023-26438 | 1 Open-xchange | 1 Open-xchange Appsuite Backend | 2024-02-28 | 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. |