CVE-2024-28859 Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency
An attacker can achieve remote code execution if a developer unserializes untrusted user input, exploiting a gadget chain in the bundled Swift Mailer dependency.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-28859?
CVE-2024-28859 is a medium-severity unsafe deserialization vulnerability in FriendsOfSymfony1 symfony1, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Symfony1 is a community fork of symfony 1.4 with DIC, form enhancements, latest Swiftmailer, better performance, composer compatible and PHP 8 support. Symfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project. This vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. Symfony 1 depends on Swift Mailer which is bundled by default in vendor directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods. These methods are called when php destroys the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abuse the array access which is triggered on foreach($this->_keys ...) for any class implementing ArrayAccess interface. This may allow an attacker to execute any PHP command which leads to remote code execution. This issue has been addressed in version 1.5.18. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Weakness: CWE-502
Which versions are affected by CVE-2024-28859?
8 open source packages ship an affected version, including friendsofsymfony1/swiftmailer, friendsofsymfony1/symfony1 and swiftmailer/swiftmailer. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
friendsofsymfony1/swiftmailer Packagist | From 4.0.0 | 5.4.13 |
friendsofsymfony1/swiftmailer Packagist | From 4.0.0 | 5.4.13 |
friendsofsymfony1/swiftmailer Packagist | From 6.0.0 | 6.2.5 |
friendsofsymfony1/swiftmailer Packagist | From 6.0.0 | 6.2.5 |
friendsofsymfony1/symfony1 Packagist | From 1.3.0 | 1.5.18 |
friendsofsymfony1/symfony1 Packagist | From 1.3.0 | 1.5.18 |
2 more packages
swiftmailer/swiftmailer Packagist | From 4.0.0 | 6.2.5 |
swiftmailer/swiftmailer Packagist | From 4.0.0 | 6.2.5 |
Products include Friendsofsymfony1 Symfony1.
How do I fix CVE-2024-28859?
Upgrade friendsofsymfony1/swiftmailer to a fixed version for your release line: 5.4.13 or 6.2.5.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2024-28859 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28859 exists.
Other vulnerabilities in FriendsOfSymfony1 symfony1
Sources
Also known as CLSA-2026-1768352248, GHSA-wjv8-pxr6-5f4r.