Cyber Resilience

CVE-2023-29290

Adobe Commerce 2.3.7 … 2.4.6

Published
15 June 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0063 47th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-29290 is a medium-severity Missing Support for Integrity Check (CWE-353) vulnerability in Adobe Commerce. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Component Firmware (T1542.002); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A08:2025 Software or Data Integrity Failures

EU & UK References

Vulnerability Data

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…

more

of this issue does not require user interaction.

CWE(s)
CWE-353

Related Threats

MITRE ATT&CK Enterprise Techniques

T1542.002 Component Firmware Stealth
Adversaries may modify component firmware to persist on systems.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-39409Same product: Adobe Commerce
CVE-2023-29292Same product: Adobe Commerce
CVE-2023-29295Same product: Adobe Commerce
CVE-2024-20758Same product: Adobe Commerce
CVE-2024-39402Same product: Adobe Commerce
CVE-2023-38249Same product: Adobe Commerce
CVE-2024-39397Same product: Adobe Commerce
CVE-2024-39406Same product: Adobe Commerce
CVE-2023-38221Same product: Adobe Commerce
CVE-2024-20759Same product: Adobe Commerce

Affected Assets

adobe
commerce
2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3
adobe
magento
2.4.4, 2.4.5, 2.4.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V12.1.1
  • V17.2.2
  • V17.2.5
  • V17.2.8

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

AU-10 Non-repudiation
addresses: CWE-353

Irrefutable evidence of actions requires integrity protection to prevent tampering or alteration of records.

CM-14 Signed Components
addresses: CWE-353

Implements required signature-based integrity verification, addressing missing support for integrity checks on components.

SA-10 Developer Configuration Management
addresses: CWE-353

Requiring control over the integrity of all changes directly compels developers to implement integrity verification mechanisms rather than omitting them.

SA-18 Tamper Resistance and Detection
addresses: CWE-353

Tamper detection fundamentally depends on integrity-checking capabilities that this control mandates or strengthens.

SA-19 Component Authenticity
addresses: CWE-353

Explicitly requires support for integrity and authenticity checks on components before acceptance into the system.

SC-20 Secure Name/Address Resolution Service (Authoritative Source)
addresses: CWE-353

Supplies the integrity-check artifacts (e.g., RRSIG, DNSKEY) that were previously missing for DNS responses.

SC-33 Transmission Preparation Integrity
addresses: CWE-353

Control explicitly adds support for integrity mechanisms such as checksums during preparation, preventing attacks that rely on missing integrity checks.

SI-7 Software, Firmware, and Information Integrity
addresses: CWE-353

Directly supplies the missing integrity verification mechanism the weakness describes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-02 full match
prevents

Directly requires integrity protection for data-in-transit via checksums or equivalent mechanisms.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Cryptographic controls can provide integrity verification for transmitted data.

A.8.20 Networks security partial match
mitigates

Network security controls can mandate integrity mechanisms on transmission protocols.

A.8.21 Security of network services partial match
prevents

Security requirements for network services can require integrity checks on data in transit.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify integrity checks for data transmission.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can mandate integrity protection for communications.

A.8.28 Secure coding partial match
prevents

Secure coding standards can require integrity verification mechanisms in protocols.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-353
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-353
  • V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-353
RHEL 8 (1 rule)
  • V-230487 RHEL 8 must not have the telnet-server package installed. prevents CWE-353

References