CVE Vulnerabilities

CVE-2023-30539

Improper Access Control

Published: Apr 17, 2023 | Modified: Nov 21, 2024
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Nextcloud is a personal home server system. Depending on the set up tags and other workflows this issue can be used to limit access of others or being able to grant them access when there are system tag based files access control or files retention rules. It is recommended that the Nextcloud Server is upgraded to 24.0.11 or 25.0.5, the Nextcloud Enterprise Server to 21.0.9.11, 22.2.10.11, 23.0.12.6, 24.0.11 or 25.0.5, and the Nextcloud Files automated tagging app to 1.11.1, 1.12.1, 1.13.1, 1.14.2, 1.15.3 or 1.16.1. Users unable to upgrade should disable all workflow related apps. Users are advised to upgrade.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Nextcloud_files_automated_tagging Nextcloud 1.14.0 (including) 1.14.2 (excluding)
Nextcloud_files_automated_tagging Nextcloud 1.15.0 (including) 1.15.3 (excluding)
Nextcloud_files_automated_tagging Nextcloud 1.11.0 (including) 1.11.0 (including)
Nextcloud_files_automated_tagging Nextcloud 1.12.0 (including) 1.12.0 (including)
Nextcloud_files_automated_tagging Nextcloud 1.13.0 (including) 1.13.0 (including)
Nextcloud_files_automated_tagging Nextcloud 1.16.0 (including) 1.16.0 (including)
Nextcloud_server Nextcloud 21.0.0 (including) 21.0.9.11 (excluding)
Nextcloud_server Nextcloud 22.0.0 (including) 22.2.10.11 (excluding)
Nextcloud_server Nextcloud 23.0.0 (including) 23.0.12.6 (excluding)
Nextcloud_server Nextcloud 24.0.0 (including) 24.0.11 (excluding)
Nextcloud_server Nextcloud 25.0.0 (including) 25.0.5 (excluding)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References