CVE Vulnerabilities


Incorrect Permission Assignment for Critical Resource

Published: Jun 20, 2023 | Modified: Jan 12, 2024
CVSS 3.x
CVSS 2.x

Default permissions for a properties file were too permissive. Local system users could read potentially sensitive information. We updated the default permissions for set during package installation. No publicly available exploits are known.


The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Open-xchange_appsuite_backend Open-xchange * 7.10.6 (excluding)
Open-xchange_appsuite_backend Open-xchange 7.10.6 (including) 7.10.6 (including)
Open-xchange_appsuite_backend Open-xchange 7.10.6-revision_39 (including) 7.10.6-revision_39 (including)

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.