CVE-2023-29289 Vulnerability Analysis & Exploit Details

CVE-2023-29289
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2023-29289 could lead to major system disruptions or data loss.

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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-29289 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:L/UI:N/S:U/C:H/I:N/A:N

CVE-2023-29289 Vulnerability Summary

CVE-2023-29289: 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 XML Injection vulnerability. An attacker with low privileges can trigger a specially crafted script to a security feature bypass. Exploitation of this issue does not require user interaction.

Assessing the Risk of CVE-2023-29289

Access Complexity Graph

The exploitability of CVE-2023-29289 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-29289

CVE-2023-29289 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-29289, 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-29289, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-29289 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-29289 poses no threat to data integrity.
  • Availability: None
    CVE-2023-29289 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.109% (probability of exploit)

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

CVE-2023-29289 References

External References

CWE Common Weakness Enumeration

CWE-91

CAPEC Common Attack Pattern Enumeration and Classification

  • XML Injection CAPEC-250 An attacker utilizes crafted XML user-controllable input to probe, attack, and inject data into the XML database, using techniques similar to SQL injection. The user-controllable input can allow for unauthorized viewing of data, bypassing authentication or the front-end application for direct XML database access, and possibly altering database information.
  • XPath Injection CAPEC-83 An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that they normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.

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-29289: 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-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • 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...