CVE-2024-34111: SSRF in service connector
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: magento/community-edition (Packagist) 2.4.5-p8, 2.4.6-p6, 2.4.4-p9.
- Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 8.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to magento/community-edition (Packagist) 2.4.5-p8, 2.4.6-p6, 2.4.4-p9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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..
- Published
- Jun 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-918
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · adobe
- 6.5
- 2.3 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| adobe | commerce | cpe:2.3:a:adobe:commerce |
| adobe | commerce webhooks | cpe:2.3:a:adobe:commerce_webhooks |
| adobe | magento | cpe:2.3:a:adobe:magento |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe commerce2.3.7
- adobe commerce2.4.0
- adobe commerce2.4.1
- adobe commerce2.4.2
- adobe commerce2.4.3
- adobe commerce2.4.4
- adobe commerce2.4.5
- adobe commerce2.4.6
- adobe commerce webhooks1.2.0 and later · up to 1.4.0 inclusive
- adobe magento2.4.4
- adobe magento2.4.5
- adobe magento2.4.6
- adobe magento2.4.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.
Adobe Adobe Commerce
- up to and including 2.4.4-p8affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | magento/community-edition | from 2.4.4 · up to and including 2.4.4 | — |
| Packagist | magento/community-edition | from 2.4.5 · up to and including 2.4.5 | — |
| Packagist | magento/community-edition | from 2.4.5-p1 · before 2.4.5-p8 | 2.4.5-p8 |
| Packagist | magento/community-edition | from 2.4.6 · up to and including 2.4.6 | — |
| Packagist | magento/community-edition | from 2.4.6-p1 · before 2.4.6-p6 | 2.4.6-p6 |
| Packagist | magento/community-edition | from 2.4.7 · up to and including 2.4.7 | — |
| Packagist | magento/community-edition | before 2.4.4-p9 | 2.4.4-p9 |
Same product
adobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV99Now
- CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV99Now
- CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV94Now
Published before and after this one in the same product
- ← EarlierCVE-2024-34109Jun 13, 2024 · Adobe Commerce | Improper Input Validation (CWE-20)28Monitor
- ← EarlierCVE-2024-34110Jun 13, 2024 · RCE in the Adobe Commerce Webhook module through a legit webhook definition28Monitor
- Later →CVE-2024-39397Aug 14, 2024 · Adobe Commerce | Unrestricted Upload of File with Dangerous Type (CWE-434)36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:magento/community-edition | 2.4.4-p9 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.5-p8 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.6-p6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-49521152 days apartAdobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)30Monitor
- CVE-2023-26366244 days apartValidate Your Inputs | Server-Side Request Forgery (SSRF) (CWE-918)27Monitor
- CVE-2024-45119119 days apartAdobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)19Monitor
- CVE-2023-29291364 days apartServer Side Request Forgery (SSRF) in USPS carrier integration configuration19Monitor
- CVE-2023-29292364 days apartServer Side Request Forgery (SSRF) in FedEx carrier integration configuration19Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-341030 days apartCustomer account takeover via web API call & subsequent password reset32Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0708 · Jun 14, 2024(Adobe Commerce Güvenlik Bildirimi )
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.