CVE Vulnerabilities

CVE-2022-34255

Improper Access Control

Published: Aug 16, 2022 | Modified: Oct 26, 2022
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

Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Access Control vulnerability that could result in Privilege escalation. An attacker with a low privilege account could leverage this vulnerability to perform an account takeover for a victim. Exploitation of this issue does not require user interaction.

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
Commerce Adobe 2.3.0 (including) 2.3.7 (excluding)
Commerce Adobe 2.4.0 (including) 2.4.3 (excluding)
Commerce Adobe 2.3.7 (including) 2.3.7 (including)
Commerce Adobe 2.3.7-p1 (including) 2.3.7-p1 (including)
Commerce Adobe 2.3.7-p2 (including) 2.3.7-p2 (including)
Commerce Adobe 2.3.7-p3 (including) 2.3.7-p3 (including)
Commerce Adobe 2.4.3 (including) 2.4.3 (including)
Commerce Adobe 2.4.3-p1 (including) 2.4.3-p1 (including)
Commerce Adobe 2.4.3-p2 (including) 2.4.3-p2 (including)
Commerce Adobe 2.4.4 (including) 2.4.4 (including)
Magento Magento 2.3.0 (including) 2.3.7 (excluding)
Magento Magento 2.4.0 (including) 2.4.3 (excluding)
Magento Magento 2.3.7 (including) 2.3.7 (including)
Magento Magento 2.3.7-p1 (including) 2.3.7-p1 (including)
Magento Magento 2.3.7-p2 (including) 2.3.7-p2 (including)
Magento Magento 2.3.7-p3 (including) 2.3.7-p3 (including)
Magento Magento 2.4.3 (including) 2.4.3 (including)
Magento Magento 2.4.3-p1 (including) 2.4.3-p1 (including)
Magento Magento 2.4.3-p2 (including) 2.4.3-p2 (including)
Magento Magento 2.4.4 (including) 2.4.4 (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