Unauthenticated code execution via dangerous file upload
Published Aug 14, 2024 · Updated Sep 16, 2024
Dangerous file upload in Adobe Commerce 2.4.7-p1 and earlier allows remote attackers to execute arbitrary server-side code. Adobe has not disclosed the upload endpoint or validation routine; the exposed path accepts a malicious file type that Apache can execute. Exploitation is unauthenticated and requires no user interaction, but it has high attack complexity and applies only to deployments using Apache.
Summary
What happened
Dangerous file upload in Adobe Commerce 2.4.7-p1 and earlier allows remote attackers to execute arbitrary server-side code. Adobe has not disclosed the upload endpoint or validation routine; the exposed path accepts a malicious file type that Apache can execute. Exploitation is unauthenticated and requires no user interaction, but it has high attack complexity and applies only to deployments using Apache.
The record
- CVE
- CVE-2024-39397
- Published
- Aug 14, 2024
- Updated
- Sep 16, 2024
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2024CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.4-p9
- Affected versionversion=0 <=2.4.5-p8
- Affected versionversion=0 <=2.4.6-p6
- Affected versionversion=0 <=2.4.7-p1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo