# CVE-2024-45120: Adobe Commerce | Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) > Attackers can bypass security features in Adobe Commerce by exploiting a race condition, requiring user interaction to alter resource states. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Oct 2024 - **Updated:** 12 Dec 2024 - **Also known as:** GHSA-47jp-46c9-25vf ## What is CVE-2024-45120? CVE-2024-45120 is a low-severity vulnerability in Adobe Commerce, published on 10 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by a Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability that could lead to a security feature bypass. An attacker could exploit this vulnerability to alter a condition between the check and the use of a resource, having a low impact on integrity. Exploitation of this issue requires user interaction. Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) ## Which versions are affected by CVE-2024-45120? 10 open source packages ship an affected version, including magento/community-edition. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `magento/community-edition` | Packagist | All versions | None | | `magento/community-edition` | Packagist | All versions | None | | `magento/community-edition` | Packagist | All versions | 2.4.4-p11 | | `magento/community-edition` | Packagist | All versions | 2.4.4-p11 | | `magento/community-edition` | Packagist | From 2.4.5-p1 | 2.4.5-p10 | | `magento/community-edition` | Packagist | From 2.4.5-p1 | 2.4.5-p10 | | `magento/community-edition` | Packagist | From 2.4.6-p1 | 2.4.6-p8 | | `magento/community-edition` | Packagist | From 2.4.6-p1 | 2.4.6-p8 | | `magento/community-edition` | Packagist | From 2.4.7-beta1 | 2.4.7-p3 | | `magento/community-edition` | Packagist | From 2.4.7-beta1 | 2.4.7-p3 | Products: Adobe Commerce, Adobe Commerce B2b, Adobe Magento. ## How do I fix CVE-2024-45120? Upgrade magento/community-edition to a fixed version for your release line: 2.4.4-p11, 2.4.5-p10, 2.4.6-p8 or 2.4.7-p3. ## Is CVE-2024-45120 being exploited? There is no known exploitation of CVE-2024-45120 in the wild and no public exploit code. ## Other vulnerabilities in Adobe Commerce - [CVE-2026-75650](https://insights.sbomify.com/CVE-2026-75650/): Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine (critical 10.0, exploited in the wild) - [CVE-2024-34102](https://insights.sbomify.com/CVE-2024-34102/): Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) (critical 9.8, exploited in the wild) - [CVE-2022-24086](https://insights.sbomify.com/CVE-2022-24086/): Adobe Commerce and Magento Open Source Improper Input Validation (critical 9.8, exploited in the wild) - [CVE-2026-48356](https://insights.sbomify.com/CVE-2026-48356/): Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type (critical 9.3, exploited in the wild) - [CVE-2026-71362](https://insights.sbomify.com/CVE-2026-71362/): Adobe Commerce and Magento Incorrect Authorization Vulnerability (critical 9.1, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-45120 and fix it if it is affected. What it is: CVE-2024-45120 is a low-severity vulnerability in Adobe Commerce, published on 10 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-45120 in the wild and no public exploit code. Affected packages and fixed versions: - magento/community-edition (Packagist): affected all versions; no fix listed - magento/community-edition (Packagist): affected all versions; no fix listed - magento/community-edition (Packagist): affected all versions; fixed in 2.4.4-p11 - magento/community-edition (Packagist): affected all versions; fixed in 2.4.4-p11 - magento/community-edition (Packagist): affected from 2.4.5-p1; fixed in 2.4.5-p10 - magento/community-edition (Packagist): affected from 2.4.5-p1; fixed in 2.4.5-p10 - magento/community-edition (Packagist): affected from 2.4.6-p1; fixed in 2.4.6-p8 - magento/community-edition (Packagist): affected from 2.4.6-p1; fixed in 2.4.6-p8 - magento/community-edition (Packagist): affected from 2.4.7-beta1; fixed in 2.4.7-p3 - magento/community-edition (Packagist): affected from 2.4.7-beta1; fixed in 2.4.7-p3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-45120/ (Markdown: https://insights.sbomify.com/CVE-2024-45120/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45120 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45120 - OSV: https://osv.dev/vulnerability/CVE-2024-45120 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-45120/ Summaries are generated and may contain mistakes; the official description above is the record.