Disputed object injection via POST attachment deserialization
Published Jun 20, 2020 · Updated Aug 4, 2024
PHP object injection in SquirrelMail 1.4.22 allows remote authenticated users to cause unspecified impact via a crafted HTTP POST. In compose.php, the $attachments value taken from POST data is passed to PHP's unserialize() function without a safe serialization format. The SquirrelMail project states that required magic methods and attack-relevant loaded classes are absent, so it considers all versions unaffected and the claimed object-injection consequence unachievable.
Summary
What happened
PHP object injection in SquirrelMail 1.4.22 allows remote authenticated users to cause unspecified impact via a crafted HTTP POST. In compose.php, the $attachments value taken from POST data is passed to PHP's unserialize() function without a safe serialization format. The SquirrelMail project states that required magic methods and attack-relevant loaded classes are absent, so it considers all versions unaffected and the claimed object-injection consequence unachievable.
The record
- CVE
- CVE-2020-14933
- Published
- Jun 20, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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