CVE Vulnerabilities

CVE-2024-37883

Improper Access Control

Published: Jun 14, 2024 | Modified: Nov 21, 2024
CVSS 3.x
4.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Nextcloud Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud. A user with access to a deck board was able to access comments and attachments of already deleted cards. It is recommended that the Nextcloud Deck app is upgraded to 1.6.6 or 1.7.5 or 1.8.7 or 1.9.6 or 1.11.3 or 1.12.1.

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
Deck Nextcloud 1.6.0 (including) 1.6.6 (excluding)
Deck Nextcloud 1.7.0 (including) 1.7.5 (excluding)
Deck Nextcloud 1.8.0 (including) 1.8.7 (excluding)
Deck Nextcloud 1.9.0 (including) 1.9.6 (excluding)
Deck Nextcloud 1.11.0 (including) 1.11.3 (excluding)
Deck Nextcloud 1.12.0 (including) 1.12.0 (including)
Deck Nextcloud 1.12.0-beta1 (including) 1.12.0-beta1 (including)
Deck Nextcloud 1.12.0-beta2 (including) 1.12.0-beta2 (including)
Deck Nextcloud 1.12.0-beta3 (including) 1.12.0-beta3 (including)
Deck Nextcloud 1.12.0-beta4 (including) 1.12.0-beta4 (including)
Deck Nextcloud 1.12.0-beta5 (including) 1.12.0-beta5 (including)

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