CVE Vulnerabilities

CVE-2023-43040

Insufficient Granularity of Access Control

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

IBM Spectrum Fusion HCI 2.5.2 through 2.7.2 could allow an attacker to perform unauthorized actions in RGW for Ceph due to improper bucket access. IBM X-Force ID: 266807.

Weakness

The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.

Affected Software

Name Vendor Start Version End Version
Red Hat Ceph Storage 5.3 RedHat ceph-2:16.2.10-248.el8cp *
Red Hat Ceph Storage 5.3 RedHat ceph-ansible-0:6.0.28.7-1.el8cp *
Red Hat Ceph Storage 5.3 RedHat haproxy-0:2.2.19-5.el8cp *
Red Hat Ceph Storage 6.1 RedHat ceph-2:17.2.6-148.el9cp *
Ceph Ubuntu bionic *
Ceph Ubuntu devel *
Ceph Ubuntu esm-infra/bionic *
Ceph Ubuntu esm-infra/xenial *
Ceph Ubuntu focal *
Ceph Ubuntu jammy *
Ceph Ubuntu lunar *
Ceph Ubuntu mantic *
Ceph Ubuntu noble *
Ceph Ubuntu oracular *
Ceph Ubuntu trusty *
Ceph Ubuntu trusty/esm *
Ceph Ubuntu upstream *
Ceph Ubuntu xenial *

Extended Description

Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection. A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.

Potential Mitigations

References