# CVE-2024-34111: SSRF in service connector > A low-privilege attacker can exploit an SSRF vulnerability in Adobe Commerce to force arbitrary requests and read files from the server. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Jun 2024 - **Updated:** 7 Aug 2024 - **Also known as:** BIT-magento-2024-34111, GHSA-jmqp-r3gg-6jh3 ## What is CVE-2024-34111? CVE-2024-34111 is a medium-severity server-side request forgery vulnerability in Adobe Commerce, published on 13 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerability that could lead to arbitrary file system read. A low-privilege authenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2024-34111? 9 open source packages ship an affected version, including magento/community-edition and magento. 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-p9 | | `magento/community-edition` | Packagist | All versions | 2.4.4-p9 | | `magento/community-edition` | Packagist | From 2.4.5-p1 | 2.4.5-p8 | | `magento/community-edition` | Packagist | From 2.4.5-p1 | 2.4.5-p8 | | `magento/community-edition` | Packagist | From 2.4.6-p1 | 2.4.6-p6 | | `magento/community-edition` | Packagist | From 2.4.6-p1 | 2.4.6-p6 | | `magento` | Bitnami | From 2.4.7-alpha0 | 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 | Products: Adobe Commerce, Adobe Commerce Webhooks, Adobe Magento. ## How do I fix CVE-2024-34111? Upgrade magento/community-edition to a fixed version for your release line: 2.4.4-p9, 2.4.5-p8 or 2.4.6-p6. ## Is CVE-2024-34111 being exploited? There is no known exploitation of CVE-2024-34111 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-34111 and fix it if it is affected. What it is: CVE-2024-34111 is a medium-severity server-side request forgery vulnerability in Adobe Commerce, published on 13 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-34111 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-p9 - magento/community-edition (Packagist): affected all versions; fixed in 2.4.4-p9 - magento/community-edition (Packagist): affected from 2.4.5-p1; fixed in 2.4.5-p8 - magento/community-edition (Packagist): affected from 2.4.5-p1; fixed in 2.4.5-p8 - magento/community-edition (Packagist): affected from 2.4.6-p1; fixed in 2.4.6-p6 - magento/community-edition (Packagist): affected from 2.4.6-p1; fixed in 2.4.6-p6 - magento (Bitnami): affected from 2.4.7-alpha0; fixed in 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 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-34111/ (Markdown: https://insights.sbomify.com/CVE-2024-34111/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34111 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34111 - OSV: https://osv.dev/vulnerability/CVE-2024-34111 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-34111/ Summaries are generated and may contain mistakes; the official description above is the record.