Arbitrary code execution via Phar archive deserialization
Published Jun 10, 2020 · Updated Aug 4, 2024
Deserialization in phpMussel before 1.6.0 allows remote authenticated users to execute code by uploading a crafted Phar archive. The archive-scanning path invokes PHP's Phar wrapper on attacker-controlled archive content, causing embedded data to be deserialized. Exploitation requires file-submission access and enabled archive checking, which was the default, and executes code in the scanner's PHP process.
Summary
What happened
Deserialization in phpMussel before 1.6.0 allows remote authenticated users to execute code by uploading a crafted Phar archive. The archive-scanning path invokes PHP's Phar wrapper on attacker-controlled archive content, causing embedded data to be deserialized. Exploitation requires file-submission access and enabled archive checking, which was the default, and executes code in the scanner's PHP process.
The record
- CVE
- CVE-2020-4043
- Published
- Jun 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- phpMussel
- Product
- phpMussel
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>= 1.0.0, < 1.6.0
What conditions does exploitation require?
What is affected?
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