CVE-2023-29290 Vulnerability Analysis & Exploit Details

CVE-2023-29290
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2023-29290 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-29290 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:56 UTC
Originally published on: 🕖 15 Jun 2023, 19:15 UTC

Time between publication and last update: 524 days

CVSS Release: version 3

CVSS3 Source

psirt@adobe.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE-2023-29290 Vulnerability Summary

CVE-2023-29290: Adobe Commerce versions 2.4.6 (and earlier), 2.4.5-p2 (and earlier) and 2.4.4-p3 (and earlier) are affected by an Incorrect Authorization vulnerability that could result in a security feature bypass. An attacker could leverage this vulnerability to bypass a minor functionality. Exploitation of this issue does not require user interaction.

Assessing the Risk of CVE-2023-29290

Access Complexity Graph

The exploitability of CVE-2023-29290 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-29290

With low attack complexity and no required privileges, CVE-2023-29290 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-29290, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-29290, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2023-29290 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2023-29290 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2023-29290 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.094% (probability of exploit)

EPSS Percentile: 42.05% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 57.95% of others.

CVE-2023-29290 References

External References

CWE Common Weakness Enumeration

CWE-353

CAPEC Common Attack Pattern Enumeration and Classification

  • Subverting Environment Variable Values CAPEC-13 The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary.
  • Client-side Injection-induced Buffer Overflow CAPEC-14 This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service. This hostile service is created to deliver the correct content to the client software. For example, if the client-side application is a browser, the service will host a webpage that the browser loads.
  • Content Spoofing Via Application API Manipulation CAPEC-389 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, spam-like content, or links to the attackers' code. In general, content-spoofing within an application API can be employed to stage many different types of attacks varied based on the attackers' intent. The techniques require use of specialized software that allow the attacker to use adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system.
  • Manipulating Opaque Client-based Data Tokens CAPEC-39 In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.
  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.
  • Manipulating State CAPEC-74 The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner. State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits. If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.

Vulnerable Configurations

  • cpe:2.3:a:adobe:commerce:2.3.7:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p3:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p3:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p4:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p4:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p4-ext1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p4-ext1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.3.7:p4-ext2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.3.7:p4-ext2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.0:ext-1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.0:ext-1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.0:ext-2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.0:ext-2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.1:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.1:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.1:ext-1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.1:ext-1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.1:ext-2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.1:ext-2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.2:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.2:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.2:ext-1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.2:ext-1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.2:ext-2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.2:ext-2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.3:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.3:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.3:ext-1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.3:ext-1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.3:ext-2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.3:ext-2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.4:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.4:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.4:p1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.4:p1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.4:p2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.4:p2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.4:p3:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.4:p3:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.5:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.5:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.5:p1:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.5:p1:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.5:p2:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.5:p2:*:*:*:*:*:*
  • cpe:2.3:a:adobe:commerce:2.4.6:-:*:*:*:*:*:*
    cpe:2.3:a:adobe:commerce:2.4.6:-:*:*:*:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.4:-:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.4:-:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.4:p1:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.4:p1:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.4:p2:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.4:p2:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.4:p3:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.4:p3:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.5:-:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.5:-:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.5:p1:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.5:p1:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.5:p2:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.5:p2:*:*:open_source:*:*:*
  • cpe:2.3:a:adobe:magento:2.4.6:-:*:*:open_source:*:*:*
    cpe:2.3:a:adobe:magento:2.4.6:-:*:*:open_source:*:*:*

Protect Your Infrastructure against CVE-2023-29290: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...